How do you handle a retrospective meeting

Set the stage. ‘Set the stage’ means priming your team for discussion. … Gather data. You can approach the data gathering stage much like the beginning of the “Start, Stop, Continue” exercise. … Generate insights. … Decide what to do. … Close the Retrospective.

How do you respond to a retrospective meeting?

The Importance of Positivity. …
Think Big and Be Specific. …
Observations on the Past Create Opportunities for the Future. …
Focus on the Facts. …
Keep the Team Positive.

What happens in a retrospective meeting?

Definition: A retrospective is a meeting held after a product ships to discuss what happened during the product development and release process, with the goal of improving things in the future based on those learnings and conversations.

What should you not do in a retro?

Don’t end a retrospective and never think about it again. …
Don’t let the meeting be too negative. …
Don’t go into the meeting unprepared. …
Don’t just focus on improving at all costs and pressure the team to implement all ideas that come up during the session. …
Don’t let outsiders attend the meeting.

What are the 3 retrospective questions?

What helps you to be successful as a team?
How did you do this sprint?
Where and when did it go wrong in this sprint?
What do you expect, from who?
Which tools or techniques proved to be useful? …
What is your biggest impediment?
If you could change 1 thing, what would it be?

How do you run a good retrospective?

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.

What went good in retrospective?

A What Went Well retrospective helps scrum teams focus on how they felt they performed during a sprint. … So what practices did you excel at as a team. These will be all the things you’ll want to consider doubling down on in your next sprint or next iteration.

What anti patterns do you know of that can happen during a retrospective?

There are many ways in which a retrospective can be a failure even if it looks suitable at first glance. The top three Sprint Retrospective anti-patterns from my perspective are: not making the retrospective a safe place, unequally distributed speaking time, and a ritualized format that never changes.

How do you introduce a retrospective?

Start: actions we should start taking.
Stop: actions we should prevent or remove.
Continue: actions we should keep doing and formalize.

When should the retrospective meeting be held?

The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is at most a three-hour meeting for one-month Sprints.

Article first time published on

How often should retrospective meetings be held?

If your team hasn’t done retros before: Start running retros after every sprint. If your sprints are long, consider mid-sprint and end-of-sprint retros. If you don’t use sprints at all, you should start by running regular retrospectives every 7-10 days.

What are retrospective action items?

Action focused retrospectives are a way for your team to reflect on your past cycle of work, discuss what you’ve learned, identify specific action items to pursue, and follow through on those action items.

What's the main purpose of holding 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.

What do you put in a sprint retrospective?

Inspect how the last sprint went with regards to people, relationships, process, and tools;
Identify and order the major items that went well and potential improvements;
Create a plan for implementing improvements to the way the scrum team does its work.

How do you lead a retro?

How do I run a good retrospective? Plan enough time to do it well (1-3 hours), ask everyone to prepare in advance, start positive by focusing on success first, make it safe for people to speak their minds, and plan to take away small changes that will compound over time.

How do you prepare for a sprint retrospective?

Step 1: Prepare for a ‘Start, Stop and Continue’ retrospective. …
Step 2: Discuss what should start doing. …
Step 3: Discuss what should stop. …
Step 4: Discuss what went well. …
Step 5: Vote for the most important items. …
Step 6: Wrap up the meeting.

How do you 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.

Should managers be in a retrospective?

Managers should enable and support teams in doing retrospectives. They can ask and expect teams to improve within the possibilities and constraints of the organization, and contribute to the organization’s goals, but it is up to the team to choose how they improve and where they decide not to improve (now).

What do you say in a retro meeting?

Can you reiterate the most important thing you learned today?
How are you feeling about our next sprint now that we’ve identified these issues?
Is anyone confused or unclear on any of the items we discussed today?
Do all of our next steps make sense?

Who should not attend the retrospective?

Anyone who is not a member of the Scrum team or sprint execution team should not attend a sprint retrospective. There are two key reasons why: ❌ They are unhelpful in retrospectives because they are a few steps removed from the work (too many cooks in the kitchen)

How long should a retro take?

Quite often, teams dedicate about 30 minutes per week to reviewing the progress. In a two week sprint that might add up to an hour of time. If you’re working with one-week iterations, the chances are that long retrospectives will be unnecessary. At the same time, a monthly retrospective may take about two hours.

How long should a retrospective last?

How Long Should Sprint Retrospectives Last? 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.

How long should retro meetings be?

How long should a retrospective meeting last for? While there is no definitive answer to how long a sprint retrospective should last, the general rule of thumb is half an hour per week. So if you’re coming out of a two-week sprint, your retrospective should be roughly an hour long.

Can a team be successful without regular retrospectives?

You can’t measure the success of your retrospective without hosting another one and another one. Consistent retrospectives have been shown to increase team performance. … The more often you come together to reflect as a team, the more you will learn and grow together.

When should a retrospective meeting be held Mcq?

Generally this meeting takes place after sprint review meeting and before the sprint planing of next sprint. If you want to conduct your meeting for your kanban cycle, you can define a interval like every 15 days to schedule it.

Who facilitates sprint retrospective meeting?

The ScrumMaster can facilitate this sprint retrospective meeting by asking everyone to just shout out ideas during the scrum. The ScrumMaster can go around the room asking each person to identify any one thing to start, stop or continue.