Enable a skilled cross-functional team applies a process to develop software that accepts change and flattens the cost of change curve.
Here you can find the next sessions of this programme:
This part focuses on the understanding and mitigation of the cost of change curve in software development. The idea is to make the team understand how simplifying system complexity can reduce the cost of changes.
This part aims to give the team insights on different software development processes. The team will gain insights into how to customize their own development process to better suit their needs and work culture.
This part introduces the Pomodoro technique to enhance team productivity and manage time more efficiently.
The focus here is on equipping the product team with skills to communicate the value of their digital product effectively. This includes understanding and implementing use cases, user stories, and scenarios.
This part is geared towards the technical team, providing practical techniques to address potential design and architectural issues.
Note - This part is preferable to do in the presence
Here's the story of the 'Flatten the Curve' programme, hatched from the trials and tribulations of software development.
"I was a student at the university in 1987 and I had to take the sociology exam in September. I couldn't keep my mind focused on my book. I was constantly getting distracted. I made a humble bet with myself: 'Can you stay focused for two minutes without distraction?' I went to the kitchen, grabbed a timer and came back to my table. The timer was red and shaped like a Pomodoro (tomato in English). I wound it up to two minutes and started reading my book. When the timer rang I had won my bet against Time. Surprised, I began to ask myself why it had worked? I gradually increased the amount of time when I set the timer. I got to one hour, but that was too much. I didn't take too long to realize that, for a number of factors, the ideal unit of work was 25 minutes followed by a 2-5 minute break.
There, on that table in September 1987, I hadn't noticed yet but for the first time I had managed to turn time into an ally. Exactly at the moment when Time appeared to be such a vicious predator to me I managed to stop in front of it, and still and afraid ask this simple question: "How can you, Time, be useful to me now?
For the first time I used time instead of running away from Time. I decided to use Time, spend it to take a break, favour my mental processes, allow my mind to organize the information it had acquired in the working time and put me in the best situation to start my next Pomodoro."
There, on that table in September 1987, I hadn't noticed yet but for the first time I had managed to turn time into an ally. Exactly at the moment when Time appeared to be such a vicious predator to me I managed to stop in front of it, and still and afraid ask this simple question: "How can you, Time, be useful to me now