Written as User Stories with all the good properties of User Stories (INVEST, Definition of Done, Acceptance Criteria etc) The Actions for the next Sprint should be: Some of it may be Social, some Creative, some may lead to specific 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 the next 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. If we read the Scrum Guide, we see that 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 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |