The 12th principle of the Agile Manifesto is:
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordinglyThe Scrum Guide explicitly tells us to have a Retrospective with every sprint. However, with no real guidelines it can easily become ineffective and only done because everything must be "done".
What do I do?It is important to remember the fundamental drive as to why a Sprint Retrospective is needed to begin with - it's to 'Continually Improve'. Hubbard explains how to achieve this in three simple steps:
- Collect data
- Derive insights
- Determine actions
How do I do it?
Now that we know what we want, how do we get "data" so that we can derive insights and ultimately determine actions to improve our teams? Ask questions of course. Rogalsky reminds us that "Wording matters" and it really does. Luckily for us, InfoQ seem to have got the memo on the whole "wording" thing with these 4 great questions to ask during Sprint Retrospectives:
- What went well?
- What didn't go so well?
- What have I learned?
- What still puzzles me?
Now do it!
So there you have it, the Sprint Retrospective is absolutely critical for your Sprint as it allows your team to reflect and improve, continuously.
So what's stopping you from improving yours?