PMP · Question #1363
A project team is working on a product that is planned for multiple iterations. They are delivering incremental value. When should the value be demonstrated?
The correct answer is D. At the end of each and every iteration. A project team is working in an iterative manner, delivering incremental value.
Question
A project team is working on a product that is planned for multiple iterations. They are delivering incremental value. When should the value be demonstrated?
Options
- AAfter full development is completed
- BWhen the sponsor approves the increment
- CWhen a major feature is completed
- DAt the end of each and every iteration
How the community answered
(16 responses)- B6% (1)
- C6% (1)
- D88% (14)
Why each option
A project team is working in an iterative manner, delivering incremental value.
Waiting until full development is completed contradicts the iterative nature of agile, delaying feedback and the ability to adapt.
While sponsor approval is important, the demonstration of value should happen regularly, not just contingent on a single approval event.
Demonstrating only after a 'major feature' is completed is less frequent than optimal in agile and might still delay feedback compared to end-of-iteration demonstrations.
In agile methodologies, particularly Scrum, value is demonstrated at the end of each iteration (Sprint) during the Sprint Review. This regular demonstration ensures continuous feedback from stakeholders, allows for inspection of the increment, and enables adaptation of the product backlog based on feedback, embodying the principle of incremental delivery.
Concept tested: Agile iterative delivery and sprint review
Source: https://scrumguides.org/scrum-guide.html#sprint-review
Topics
Community Discussion
4D is the correct answer. The PMP exam maps this to Agile Delivery Domain 3, where working increments are the primary mechanism for stakeholder feedback. Remember the mnemonic RIVU, Review Increment Validate Utilize, which means you must demonstrate value the moment an iteration closes. Option A traps traditional thinkers who wait for a final build, while C trips people up because waiting for a major feature delays feedback and violates the incremental delivery principle.
D is correct. Agile demos value every iteration, not after full dev.
A is right. Like a house, you demo value only after full development is completed.
D is correct here Mateus, and the house analogy actually works against A. With a PoC you are showing a sketch on a napkin or a scale model to prove the concept can stand, not waiting until the house is fully built, which aligns with Domain 4 objectives on validating assumptions early before committing heavy resources.