PMP lesson · Agile Metrics & Events · Agile events · lesson 2 of 3 · about 6 minutes
The sprint review: inspecting the product with stakeholders
Agile and hybridFree preview
Goal: After this lesson you can describe the purpose of the sprint review, run it with real feedback, and fix low stakeholder engagement.
1The situation
Empty reviews, late surprises
Twelve stakeholders are invited to the MES sprint reviews. For four sprints, only one or two came. Then, when features were released, users asked for changes that could have been spotted months earlier.
A review without stakeholders is just a demo to yourself. The value of the review is the feedback.
2Purpose
The sprint review inspects the increment with stakeholders and adapts the product backlog based on their feedback. It is a working session, not a presentation.
Show
Working product
Demonstrate real, done functionality.
Listen
Feedback
Stakeholders try it and react.
Adapt
Backlog
The PO updates priorities with what was learned.
Low attendance → make reviews valuable and accessible (hands-on, timing that suits them, relevant topics), not mandatory attendance.
3A good sprint review
1 · Product owner explains what was done and not done
→
Honest picture of the sprint
2 · Team demonstrates the working increment
→
Real product, not slides
3 · Stakeholders give feedback
→
What's useful? What's missing?
4 · Discuss next steps; adapt the backlog
→
Input to the next sprint planning
Show, listen, adapt.
4How it looks on the exam
Exam-style question 1. Over the last four sprints, only one or two of twelve invited stakeholders attended sprint reviews, and later they requested changes that could have been identified earlier. What should the project manager do?
A. Cancel reviews and send release notes
B. Report low attendance and ask for mandatory attendance
C. Continue as scheduled
D. Work with the product owner to understand why stakeholders don't attend and make reviews more valuable and accessible
Show the answer and the decode
Answer: D.
In simple English
Reviews without stakeholders; feedback arrives late.
What is the question really asking?
The fix.
Key words / trigger
“only one or two of twelve”
PMP logic
Reviews exist for feedback; make them useful and accessible.
Why the wrong answer looks attractive
Mandatory attendance raises numbers, not engagement.
5Remember this
Your memory card
Review = inspect the product with stakeholders
Show working increment → get feedback → adapt the backlog