Retrospective

Makes patterns from a sprint visible and derives concrete improvements for the next work cycle.

Core question: What affected the quality and effectiveness of the last Sprint, and which change will we inspect next Sprint?

• Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter
• Scrum Team

Sorts team feedback into start, stop, and continue so the retrospective produces clear next steps.

Core question: What should the team start, stop, or deliberately continue doing?

• 30-60 min
• 3-12

Collects emotional signals from the team, clusters them into themes, and makes real conversation topics visible.

Core question: Which experiences made us mad, sad or glad, and which working condition do we want to change?

• 30-60 min
• 3-10

Sorts review, learning points, and friction into Liked, Learned, Lacked, and Longed For for concrete improvements.

Core question: What did we like, learn, lack, and long for, and which small improvement will we inspect afterward?

• 45–75 min
• Team members involved

Makes a team's winds, anchors, risks, and target picture visible and turns the review into prioritized improvements.

Core question: What helps our journey to the goal, what slows us today and what danger lies ahead?

• 45-90 min
• 4-12

Sorts practices into Start, Stop, More, Less, and Keep, so routine changes get chosen more deliberately.

Core question: Which practices should we preserve, increase, reduce, stop or start trying?

• 45-90 min
• 4-12

Examines an incident with a view to decisions, assumptions, and system factors, and records the resulting lessons.

Core question: What can we learn from the actual course of events without reducing the analysis to individual blame?

• 1-3 h
• 3-10