Turn the Sprint Retrospective from a tired ritual into the engine of real improvement. Learn what the event is actually for, how to run it so it produces one owned, trackable change per Sprint, and how to avoid the traps that leave teams complaining about the same thing for months.
Watch the free preview
The Sprint that never gets better — free to watch, no account needed.
What you'll learn
- Explain the purpose and timebox of the Sprint Retrospective per the Scrum Guide 2020
- Distinguish a genuine improvement action from a vague, unowned wish
- Facilitate a Retrospective that produces one or two owned, trackable improvements
- Redesign a stale Retrospective format that keeps repeating the same non-action
- Build a Retrospective Improvement Tracker that carries actions to completion
Syllabus
Why Retrospectives Matter, and What They Are For
The Sprint that never gets betterFree preview
What the Scrum Guide actually says
The Element in Depth — One Owned, Trackable Improvement
Why one action beats a wish list
What makes an action specific, owned and trackable
Applying It to Real IT Work
Facilitating a Retrospective that produces change
Case study — ten Retrospectives, same non-action
Making It Stick
Building a Retrospective Improvement Tracker
Traps and anti-patterns to avoid