Retrospectives are my favorite agile practice, and one of the most often overlooked. Reading Agile (micro)Management recently, I realized that retrospectives aren't only the key to continual improvement. Run thoughtfully and transparently, they also improve the team's engagement in the agile process.
The first few retrospectives with a new team matter most. If they're unproductive, the team starts treating them as a formality, or drops them altogether. Run well, they draw a lot out of engineers, who are curious by nature and want to improve everything around them, including how the team works.
I prefer the Stop, Start, Continue, More Of, Less Of wheel, but there are many effective retrospective techniques. To make agile work better for your team, learn the available techniques and try them out in your organization.
Keys to retrospective success
Consistency
Hold retrospectives at regular intervals, usually at the end of each sprint. Team engagement and continual improvement both depend on it. When retrospectives are infrequent, unproductive habits go unchallenged. A steady cadence keeps the current problems in view and lets the team improve quickly.
Inclusion
Include every member of the agile team. Whoever facilitates should watch the room. Quieter members can be hard to draw out, but close attention and a gentle question often bring out their best insights. If that doesn't work, check in with them after the session. Some people need time to think a point through before they're ready to share it.
Transparency
Discuss the items raised in a positive, constructive way, and make sure every team member knows the outcome. Put the notes on a screen during the session so everyone can see them, and correct or clarify them as you go. Don't sweep items under the rug.
Follow-up
When the team agrees an item should be addressed, record it in the notes as a clear action item with an owner, and follow through. Start each retrospective by reviewing the action items from the last one. If the same item comes up at every retrospective, confidence in agile slowly erodes.
Trust
Trust is what the other four build. When retrospectives are consistent, inclusive, transparent and followed up, the team comes to share responsibility for improving how it works every day.
Conclusion
Retrospectives are one of the most critical parts of an effective agile implementation. Don't just hold them regularly; make sure they're run well. That gives everyone more confidence in agile, and it ensures continual improvement is actually happening.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
From the Principles behind the Agile Manifesto.
First published February 17, 2016. Revised October 2026, adding practices from the 2024 version of this post.