How do you structure a retrospective team?
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 do you run a quarterly retrospective?
Here’s how you can run a retro with your team in 1h.
- Start with a timeline (10 mins) A common mistake that teams make is to jump straight into talking about the issues they had.
- Look at the previous retro items (15 mins)
- Brainstorm start, stop, continue (5 + 15 mins)
- Vote on Start and Stop (5 mins)
- Wrap up!
What do you say in 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.
How do I run a retrospective remote?
How to run a remote retrospective with your team
- Step 1: Create an environment of psychological safety.
- Step 2: Figure out the agenda and logistics.
- Step 3: Review the recent past.
- Step 4: Discuss candidly, but respectfully.
- Step 4: Decide what you’ll take action on before the next retrospective.
How do we do large scale retrospectives?
The facilitators spread out, pick a theme, gather a cross-section of people that have insights into that theme, and run a retrospective. Smaller groups make for better conversations, and also easier logistics (easier to find a time that works, a room that fits people, etc).
Which is the best format for an agile retrospective?
In my opinion, a successful Agile Retrospective must follow somehow this structure. This concept was introduced some years ago by Esther Derby and Diana Larsen, in their book “Agile Retrospectives. They explained to us that there are five different phases of an Agile Retrospective and this is what I want to explain to you in this post.
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.
Is it good to run retrospective with large teams?
Running a retrospective, especially with large teams, is challenging. However, with good preparation, it’s a useful tool to gather feedback and improve team spirit. Retrospectives should always be an integral part of our work. We should never forget the importance and potentials this tool gives.