Contents
How do you moderate a retrospective?
Tip 5 for moderating the retrospective: Select a simple format. Especially at the first retros, you should choose a simple, well-structured format to moderate the retrospective. For example the classics – “Keep, stop, start”, “Mad, sad, glad” or in the next step the sailing boat retrospective.
How do you facilitate an effective retrospective?
Retrospective facilitation good practices
- Establishing a open and honest culture in the meeting.
- Ensure that all team members participate in the meeting.
- Assure that the team establishes a shared understanding of how things went.
- Help the team to decide upon the vital few actions that they will take.
What does your team do during the team retrospective?
Retrospectives are used frequently to give teams the opportunity to pause and reflect on how things have been going and then, based on those reflections, identify the improvements they want to make.
How do you run a big retrospective?
Structuring a large retrospective
- Set the stage — Aim: Set the tone and direction for the retrospective.
- Gather data — Aim: Create a shared memory; highlight pertinent information and events.
- Generate insights — Aim: Think creatively; look for patterns, themes and connections.
How do you structure a Retrospective?
How to structure a retrospective
- Set the stage – Goal: Set the tone and direction for the retrospective.
- Gather data – Goal: Create a shared memory; highlight pertinent information and events.
- Generate insights – Goal: Think creatively; look for patterns, themes and connections.
How many people should be in a retrospective?
#5 To hold effective retros, start small and grow as needed While online retrospectives have no size limit, there’s no need to go crazy. Start in the range of 6-8 participants and scale up only if engagement stays high.
What should be in a retrospective?
A quick recap of sprint retrospectives
- Gather data and insights from their team (what went well, what went poorly, etc.)
- Discuss the data and insights and make action items around them.
- Make a plan for improvements on the next sprint.
When do you need to do a retrospective session?
Typically, retrospectives are held within a delivery team or a small team working on a specific topic. But sometimes, you have to run a retrospective session with larger teams — for instance, a whole project team that consists of multiple delivery teams.
What’s the best way to do a team retrospective?
Get team members to add to the lists in the week prior to the retrospective. Run through each card during the meeting to discuss and cover all items. Like all the other proposed retrospectives, the objective of this exercise is to generate as much conversation as possible.
When to have a team retrospective in scrum?
A team retrospective, or ‘retro’ for short, is a meeting typically held at the end of a project or a season, aimed at identifying what worked well, what not so well, and uncovering problem areas that the whole team can learn from and fix. This format originates in the Scrum framework, where sprint retrospectives are part of the workflow.
Why is a retrospective meeting important in agile?
Everyone knows the importance of retrospectives when it comes to agile working: it’s an essential meeting to reflect, gather feedback and identify how to improve continuously. A good retrospective strengthens the team and creates a spirit of shared identity.