Preview Mode Links will not work in preview mode

Agile Coaches' Corner shares practical concepts in an approachable way. It is for agile practitioners and business leaders seeking expert advice on improving the way they work to achieve their desired outcomes. If you have a topic you'd like discussed, email it to, or tweet it with #agilethoughtpodcast.

Apr 7, 2020

In this episode of the Trainer Talk supplemental series to the Agile Coaches' Corner Podcast, Professional Scrum Trainer Sam Falco answers the questions: Do Sprint Reviews and Sprint Retrospectives Overlap?

Why do we talk about what went well in a Sprint Review?

In a Professional Scrum Foundations class I taught recently, one of my students asked if there was an overlap between the Sprint Review and the Sprint Retrospective. She was reacting specifically to the statement from the Scrum Guide that in Sprint Planning, “The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved.” Doesn’t that discussion properly belong to the Sprint Retrospective?

It’s easy to see how someone could be confused by that statement in the Scrum Guide. After all, a common format for Retrospectives is “What went well, what could have gone better, and what could we do differently?”

The Intent of a Retrospective

The difference is in the intent. In the Sprint Retrospective, the Development Team is focused on how it can improve its work. Whether that has to do with the way we work together, the tools we use, improving our Definition of Done, or some process we’re using, the goal of the Retrospective is to produce improvements it can introduce into the next Sprint.

The Intent of a Sprint Review

By contrast, the focus of Sprint Review is to collaborate on the most valuable thing we can do next with regard to the product. When the Development Team talks about what went well and what problems it ran into in this context, it is valuable feedback to the Product Owner and stakeholders about the nature of their work—facts that ought to be taken into account when creating and ordering Product Backlog items.

Provide Feedback

Let us know what you thought about this supplemental episode of the Agile Coaches’ Corner. If you’re interested in training, visit or call us at 877.514.9180 to learn more. And if you have a question you want us to answer on the next Trainer Talk episode, email us at

Want to Learn More or Get in Touch?

Register for our upcoming AgileThought Virtual Community events: "Working Agreements Workshop" and Kanban for Work and Home"

See available training courses at

Visit the website and catch up with all the episodes at!

Email your thoughts or suggestions to or Tweet @AgileThought using #AgileThoughtPodcast!