Skip to main content

What should I say in retrospective meeting?

A good retrospective, according to Scrum Guide, should:
  • 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; and,
  • Create a plan for implementing improvements to the way the Scrum Team does its work.

Similarly, it is asked, what went well in retrospective meeting?

The basic structure of a retrospective or debrief is to surface the following in a brief meeting of the whole team: What went well (you'll want to keep doing these things) What could be improved (went OK, but could be better)

Similarly, how do you make a retrospective fun? Here are a few ways that you can encourage the team to adopt a different perspective and thus disrupt the usual flow:

  1. Put on a creative and innovative hat.
  2. Change the facilitator.
  3. Change the style.
  4. Come prepared with some data.
  5. Follow up on the retrospective action items!

Simply so, how do you start a retrospective meeting?

And there's certainly more than one way to run a Retrospective. The best way to keep Retrospectives productive is to continuously challenge the team to think of solutions in new and interesting ways. The Agile Retrospectives

  1. Set the Stage.
  2. Gather Data.
  3. Generate Insights.
  4. Decide What to Do.
  5. Close the Retrospective.

What is a retrospective question?

In short, a 4 Question Retrospective gets the the team to reflect on the last, short period of time working together (often 2 weeks) and answer four specific questions: What went well? What didn't go so well? What have I learned? What still puzzles me?

Similar Question and The Answer

What is the point of a retrospective?

How do you write a retrospective?

What is a retrospective summary?

What do you think is a good way for team members to remain updated?

What is meant by iteration goal?

What is Agile retro?

How do you do a sprint retrospective?

What do you put in a sprint retrospective?

How does the team know what to work upon?

What is the main role of the product owner?

What is a sprint?

What is the difference between lessons learned and retrospectives?

What is the key to a successful retrospective activity?

How do you use retrospective?