LEARN. PRACTICE. GROW.Concept and mechanism
At Sprint Review, an operations team discovers that a new file search returns correct results but does not help identify the next action. That feedback concerns the product and user outcome. At retrospective, the team observes that checks started too late and work accumulated near Sprint end. That observation informs improvements in ways of working. The conversations are related but do not inspect the same thing.
Guided application
A useful Review involves stakeholders collaborating on product and context changes. It can lead to new backlog choices rather than a slide sequence where priorities cannot be questioned. At retrospective, turn “communicate better” into an observable experiment: arrange an earlier joint check and observe waiting queues. Next Sprint, inspect its effect before concluding the practice improved matters. If the Sprint Goal becomes obsolete, cancellation authority belongs to the Product Owner, considering the context.
The team experiments with failure-scenario checks mid-Sprint and observes whether last-day blocked work decreases.
Common pitfalls
Treating feedback as mere approval; creating vague actions without checking effects; canceling a Sprint solely because an estimate was missed.
Related topics: Empiricism and values in real decisions · Self-management with clear accountabilities
Learning needs to reach a decision and be inspected again.
Reference: The Scrum Guide, November 2020 · PSM I; Scrum Guide November 2020; no public numbered exam revision