In our previous article on Agile meetings we discussed the Sprint Review. Let’s take a look at what happens next.
Scrum is an empirical framework. This is because we want people to take Agile’s manifesto, values, principles and practices, implement them and then build upon them. Regular retrospection enables us to continuously improve our way of working.
A retrospective meeting looks initially at the sprint time box, but can also be used in a broader context, for example across projects or releases. We can use these meetings to deep dive into problems and assess what happened. The key outcome is to define what causes problems and to take action, therefore improving the process.
Retrospectives are usually the most undervalued session and seen by some as a waste of time. However they are the most important thing we will do as a company because they enable us to do our work better and faster next time. Why cut a tree down with a blunt saw when you can sharpen it first?
Scrum masters look for innovative ways to keep the format fresh and to mine information on what needs to change. They then ensure that actions are resolved. By doing this we can make sure that we offer the best possible service to our customers.
So, we’ve now covered all the key scrum meetings. There are plenty of other practices we use – look out for upcoming posts.