Facilitate, direct and intervene in the Retrospective discussion just enough and just in time to keep it useful, but not more. Don’t skip it and do your best to have it in the same day, at the same time, to establish a predictable rhythm.Īs anything else in agile, your intervention as a Scrum Master should be “ Just Enough, Just in Time”.
Retrospective template how to#
How to organize and facilitate the Retrospective as the Scrum Masterįirst key point is to consistently organize the Retro meeting every Sprint.
Some of it may be Social, some Creative, some may lead to specific Actions for next SprintĬlose by reviewing the list of agreed Actions for next Sprint
Specific and clear enough to give structure and encourage participationĪt the same time, flexible enough to allow for ad hoc interaction and creativityĮxample agenda for a one hour Retrospective:ġ0 min: Review progress on actions agreed last Retrospective (ideally, they should all be done, since actions taken at Retro’s are actions we plan to do in one Sprint)ġ5 min: Starfish exercise (or similar) to extract ideas, suggestions and feedback for this meetingģ5 min: Discuss starfish output. You need an Agenda: Here’s one you can useįreestyle Retrospective meetings that rely on the team members simply saying and debating things without any structure really don’t work well unless the team is exceptionally mature. The right balance might vary from team to team or during the lifetime of the team, but all three are required. On the other hand, Retrospectives that are exclusively action driven and “too serious” leave no room for Social and Creative will feel too much like “regular work” and enthusiasm and participation will be low. Retrospective that cater to Social only are good avenues to let steam off, but in the absence of actions they will start to feel pointless and ineffective. I don’t think a retrospective works well without catering for all these 3 objectives. Specific improvement actions that are small enough to be planned for the next sprint A place and time to brainstorm, consider new ideas, come up with new perspective A safe place for any and all team members to express appreciation, frustration, satisfaction, confusion or any other positive or negative feelings they may have about the Sprint that just endedĬreative. My objectives for a good Retrospective meeting are: The 3 Objectives of the Retrospective Meeting It’s not the only way to do it, but I think it’s a good starting point for most teams. This article is about defining a clear template for what you want to achieve in the Retrospective and how you want to organize and run it. There’s many activities, games and tools you could use in the Retrospective meting, and googling for them will swamp you with results. It’s the continuous improvement meeting, it closes the sprint long learning feedback loop, it’s not about the work but about how we work, and it’s owned by the team, but that’s about it. It’s not as well defined as the other Scrum meetings, like Sprint Planning for example. The Scrum Retrospective meeting is one of the more “mysterious” Scrum meetings.
0 kommentar(er)
