HKSM
Demonstrate and Validate Sprint
This process has the Scrum Team showcase the Sprint's completed deliverables to the Product Owner and key business stakeholders during the Sprint Review to confirm they meet expectations and gather feedback for acceptance or follow-up changes.
Key Points
- Held at the end of each Sprint as the Sprint Review meeting.
- The team demonstrates a working, potentially shippable increment to the Product Owner and stakeholders.
- Acceptance is based on agreed criteria; feedback and gaps are captured for future backlog updates.
- Outcomes may include updated Product Backlog, revised release plans, and shared understanding of what is done.
Example
At the Sprint Review, the team walks the Product Owner and marketing stakeholders through the new checkout flow, shows it working on web and mobile, verifies each acceptance criterion, receives feedback on UI polish, and logs two minor changes into the Product Backlog.
PMP Example Question
Which action best describes the Demonstrate and Validate Sprint process?
- The team presents the completed increment to the Product Owner and stakeholders to confirm it meets acceptance criteria.
- The team decomposes Product Backlog items into tasks for the next Sprint.
- The Scrum Master removes impediments identified by the team.
- The Product Owner reorders the Product Backlog without stakeholder input.
Correct Answer: A — Presenting the Sprint deliverables to stakeholders for review and acceptance
Explanation: Demonstrate and Validate Sprint is the Sprint Review where the increment is shown, validated against acceptance criteria, and feedback is captured.
