Scrum events · a focused study break
Sprint Review vs
Sprint Retrospective.
You know the names. Can you explain which conversation belongs where? Work through three original scenarios, then check your reasoning against the Scrum Guide.
Sprint ReviewWhat should the product do next?The Scrum Team and stakeholders inspect the outcome and consider adaptations.
Sprint RetrospectiveHow can we work more effectively?The Scrum Team considers improvements to quality and effectiveness.
Source: Scrum Guide — Sprint Review and Sprint Retrospective.
Try the distinction.
Read each situation and choose an answer before opening the explanation. These are learning exercises, not certification questions or a readiness score.
Scenario 1 · A new opportunityThe feature works. The context has changed.
A team demonstrates a new appointment reminder. Clinic staff explain that cancellations, rather than missed reminders, now create their biggest scheduling problem. Which event is designed for discussing what that means for the product’s direction?
- Sprint Review
- Sprint Retrospective
Check the reasoning
A — Sprint Review. Stakeholder feedback and changed circumstances inform what the product should do next. This working session can lead to Product Backlog adjustments.
Read the Sprint Review section →
Scenario 2 · A recurring delayThe team keeps finding the same bottleneck.
Across the Sprint, Developers repeatedly waited for access to a shared test environment. The Scrum Team wants to examine how its tools and collaboration contributed to that delay. Which event is designed for this inspection?
- Sprint Review
- Sprint Retrospective
Check the reasoning
B — Sprint Retrospective. Tools, interactions and processes are among its inspection topics. Improvements can be addressed sooner; the team need not wait for this event to act.
Read the Sprint Retrospective section →
Scenario 3 · A release decisionThe improvement is ready on Tuesday.
An accessibility improvement meets the product’s Definition of Done. The Sprint Review is on Friday. Does Scrum require the team to wait until that meeting before releasing the improvement?
- Yes — the Sprint Review is the required release gate.
- No — an Increment can be released before the Sprint ends.
Check the reasoning
B — No required wait. The Sprint Review is not a release gate. An Increment may be delivered beforehand; work must meet the Definition of Done.
Read the Increment section →
Continue in Scrum Assessments App
Make the explanation part of your practice.
Study with original questions, explanations and named Scrum Guide references on iPhone or iPad. Practise offline, without creating an account.
Start with Free
Try explained practice samples and a full simulation every seven days. Keep your attempt history and see current Topic Signals.
Use Premium for deeper practice
Unlock the full released question library, unlimited sessions, topic-focused practice, topic trends and matching attempt comparisons.
View the free app on the App Store →Free download with optional auto-renewing Premium subscriptions. Check local prices and device requirements on the App Store.
Before you continue
Is this an official PSM I assessment?
No. This is independent learning material. Scrum Assessments App is not affiliated with or endorsed by Scrum.org. These original examples are not real, recalled or reconstructed certification questions. No exam result is guaranteed.
Where should I start with the framework itself?
Read the Scrum Guide. You can also use Scrum.org’s free Scrum Open. Use this page and the app as additional practice.