Contents
How can I make my retrospective better?
6 Tips for Better Product Retrospective Meetings
- Create a safe space.
- Make retrospectives a habit.
- Don’t forget to look at the positives.
- Think outside the office.
- Bring in backup.
- Sometimes your product retrospective meetings need retrospectives of their own.
How long should a retrospective last?
The second rule is that the sprint retrospective should take between 60 to 90 minutes for a two-week sprint and likely a bit longer (however, probably not proportionally longer) when doing longer sprints.
What is the goal of a retrospective?
A Retrospective is a ceremony held at the end of each iteration in an agile project. The general purpose is to allow the team, as a group, to evaluate its past working cycle. In addition, it’s an important moment to gather feedback on what went well and what did not.
How long should a scrum retrospective be?
Sprint retrospectives are limited to a maximum of three hours. The general guidance is to allow 45 minutes for each week of sprint length. So a two-week sprint would cap the sprint retrospective at an hour and a half; a four-week sprint at three hours.
What makes a good retrospective for Scrum.org?
A clear, inspiring and ambitious purpose will invite the team to continuously improve themselves. Without a purpose, the team is at risk to become Scrum zombies that only “mechanically” attend the Retrospective. 3. The Constellation Game*
What’s the best way to walk out of a retrospective?
Many teams walk out of the retrospective and immediately forget about it, which is a huge waste. A better approach is to walk out with 1 or 2 specific actions that the team agrees to pursue. Some teams simply add the actions from each retro to a growing list of items that no one does anything about or even sees.
What’s the best way to spice up a retrospective?
11 Ideas to Spice up Your Retrospective. 1 1. The Feedback Game. 2 2. Discuss the Team’s Purpose. 3 3. The Constellation Game*. 4 4. Why Retrospectives?*. 5 5. Expectations*.
What should be included in a sprint retrospective?
The first nine list items are among them. The last two are, in my mind, too often overlooked and can be the most powerful. While having a plan for the Sprint Retrospective is good practice. Far too often the event becomes the Scrum Master show.