Improvement

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

Compares goal and actual course, identifies deviations, and records concrete learning steps.

Core question: What was meant to happen, what actually happened, what can we learn, and what should we change or sustain?

• 20-45 min
• 3-12

Visualizes workflows with roles and handoffs so problems, media breaks, and improvement opportunities become visible.

Core question: What happens from trigger to outcome, where do decisions and handoffs occur, and what evidence supports change?

• 1-3 h
• 3-10

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

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

Finds a system's bottleneck, aligns work around it, and cyclically checks whether flow improves.

Core question: Which constraint currently limits the system goal, and how will we exploit, subordinate, and elevate it?

• 2-4 h Analyse, laufend
• 3-12

Moves team boundaries, interfaces, and collaboration toward a concrete result through "explain the scale and categories", "run an anonymous team survey", and "derive and track actions".

Core question: Which load currently blocks sustainable flow, and what system change will reduce it?

• 60-90 min
• 3-12