Leitfaden für die Retrospektive des Scrum Masters

A sprint retrospective is the Scrum meeting where a team reflects on the last sprint and agrees improvements. Learn who attends, the 5 stages, and how long it runs.

Retrospectives drive continuous improvement: see the purpose, the cost of skipping them, and what a well-run retro delivers for your agile team.

The Retrospective Prime Directive is a statement that assumes everyone did their best. See what it says, why it matters, and how it sets a blameless tone.

Online and in-person retrospectives share the same agile goals but differ in logistics. Compare the pros, the cons, and what stays the same for both.

When your team is distributed, the remote retrospective becomes an even more vital agile ceremony. See how it rebuilds connection, accountability and trust.

Run a great online retrospective with remote teams: allow time to connect, set clear etiquette, use real-time feedback, check the tech, and keep the basics.

Use this practical before, during, and after checklist to make sure your agile retrospective runs smoothly and ends with clear, tracked action items.

Browse free retrospective templates — agile, fun, process, product, and bad-sprint recovery — and learn how to pick the right one for your team.

Agile games build high-performing teams. See what they are, why they work, the research behind them, and a categorised list of games to play with examples.

Help your team give honest feedback. Learn the signs your team lacks psychological safety and the steps a Scrum Master can take to build it in retros.

Scrum has four ceremonies (now called events): Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective. Learn the purpose, timebox, and attendees of each.

The Sprint Review inspects the product with stakeholders; the Sprint Retrospective improves how the team works. Learn the difference, who attends, and why you need both.

Scrum has five values: Commitment, Focus, Openness, Respect, and Courage. Learn what each one means in practice and how a retrospective brings them to life.

Scrum has three roles: the Product Owner, the Scrum Master, and the Developers. Learn what each is accountable for and how they work together as one Scrum Team.

Scrum has three artifacts: the Product Backlog, the Sprint Backlog, and the Increment. Learn what each one is, its commitment, and how they create transparency.

Story points estimate the effort, complexity, and uncertainty of work — not hours. Learn how relative estimation, planning poker, and velocity fit together.

A burndown chart shows work remaining against time. Learn to read the ideal vs actual line, the difference from a burnup chart, and what it reveals in a sprint.