2023-07-04 00:00:00
Organisations strive to have high-performing teams delivering value regularly. They are looking to deliver faster and do more for less, to keep ahead of their competition and save costs.
However, this isn’t easy. Teams take time to become high performing. Adopting an Agile Project Management approach and harnessing a continuous improvement culture will make all the difference.
Let’s get started with the definition of continuous improvement: it’s the process of making regular small changes and incremental improvements.
Developing a continuous improvement culture, where learning and adapting is ingrained into a team links to the core of Agile Project Management and the Agile principles.
Adopting continuous improvement principles can give numerous benefits to any team, including:
Adopting Continuous Improvement is a great goal to have. However, it can be tricky to know where to start and set teams up for success. Adopting these principles can help:
Adopting these working practices builds on the principles:
Type of Retro | Description |
---|---|
Four Ls | This format can be particularly insightful. The four L’s stand for Liked, Learned, Lacked, and Longed for. It’s best to get feedback from each team member at a time for each of the four L’s and then see what patterns or themes come up. |
Sailboat | This metaphor is a good way to help structure your retro. The team will compare their last sprint to a sailboat and identify what propelled it forward (like wind) and what held it back (like anchors). Improvement areas are likely to come from what held it back, but likewise, improving further what is propelling it forward is a good way to build on positive actions. |
Start, Stop, Continue | This structure is great at turning a discussion into action. The team collaborates to determine what actions they should start doing, stop doing, and continue doing in future sprints. |
Working and Stuck | This is a simple method to help the team focus on things that are working and stuck. Things that are currently working (positive, neutral, even sliding into negative) and will continue to work in the next sprint. Some things might not be ideal but are still working. These could be great candidates for improvement. The stuck category is for things that are blocked, hampered, or reduce the team’s efficiency. These are areas to improve. |
What went well | Another simple format to help the team focus on what went well and what didn’t go so well in the last sprint. It helps the team focus on outcomes and allows broader discussions with a lightweight structure to help shape them. |
Start small: There is always room for improvement, so review how you are currently working. Once you have feedback, decide where to improve, remembering to keep the improvement small and then commit to it as a team. Implementing one small improvement each sprint can build positive momentum. Add this improvement as a story to an upcoming sprint and complete it as you would a feature story. Big issues often seem too large to tackle, try to break them down, identify small improvements, to tackle them in stages.
Metric | Description |
---|---|
Value | What constitutes value differs for different teams. Measuring it is really important to understand whether your delivery is hitting the mark with your customers. Customer satisfaction, increasing customer/user activity, retention rates, conversion rates, or response rates can be great ways to track value. There will be many. Define what matters to you and your customers and track it. This metric encourages customer feedback and conversation on how the team is doing. |
Velocity | The number of story points completed in a sprint. It’s good to measure team capacity alongside this to provide context on how much time the team had to work on stories in the sprint. |
Work in Progress | The number of work items started but not finished. Great insight comes from understanding how much, and for how long, the team has work in progress. Teams often start a lot of stories in a sprint and then struggle to finish them. If this is something your teams do, introduce limits on work in progress and focus on only having a minimal number of stories in progress. |
Cycle Time | Actual time spent on a work item from the start of the first task to the end of the last task. This helps identify if there are blockers, issues, or unexpected delays in your processes. |
Throughput | The number of work items completed in a sprint. The larger the number the better. This depends on the size of the items and encourages work to be broken down. |
Improvements | Tracking improvements identified and implemented over time is very insightful. Tracking what impact the improvement made is a good way to see tangible results. |
Adopting the principles and practices in this post should help you and your teams continuously improve.
Encouraging an open mindset, regular communication, measurement and improvement, and a focus on continuous feedback, is the best way to drive a culture where everyone is striving to find the next improvement opportunity, to deliver greater value for customers.