PMP · Question #728
During the setup of an agile project, the product owner expressed clear interest in having features released during product development over having the product completed in one year. What should the p
The correct answer is B. Facilitate sprint planning sessions with a focus on defining the minimum viable product (MVP). To fulfill the product owner's desire for early feature releases in an agile project, the project manager should facilitate sprint planning sessions focused on defining the Minimum Viable Product (MVP). This strategy prioritizes the delivery of the highest value features first, e
Question
During the setup of an agile project, the product owner expressed clear interest in having features released during product development over having the product completed in one year. What should the project manager do?
Options
- ADesign a set of metrics including velocity, which is a good measure of value delivered.
- BFacilitate sprint planning sessions with a focus on defining the minimum viable product (MVP)
- CPromote a productive environment where everybody can work without interruptions from the rest
- DCreate a reward system recognizing group contributions to get people motivated and improve
How the community answered
(24 responses)- A13% (3)
- B79% (19)
- C4% (1)
- D4% (1)
Why each option
To fulfill the product owner's desire for early feature releases in an agile project, the project manager should facilitate sprint planning sessions focused on defining the Minimum Viable Product (MVP). This strategy prioritizes the delivery of the highest value features first, enabling early user feedback.
While velocity is a useful agile metric, simply designing metrics doesn't directly address the product owner's immediate goal of early feature releases; MVP definition is a more direct and actionable step.
The product owner's desire for early feature releases aligns perfectly with the agile concept of delivering value incrementally. Facilitating sprint planning sessions that focus on defining and prioritizing the Minimum Viable Product (MVP) ensures the team concentrates on building and releasing the most essential features first, enabling early user feedback and demonstrating progress.
Promoting a productive environment is a general good practice but doesn't specifically target the product owner's request for early feature releases and value delivery.
Creating a reward system is a motivational tool but is not the primary mechanism for planning and executing work to achieve early feature releases in an agile context.
Concept tested: Agile principles (MVP, early value delivery)
Source: https://www.pmi.org/agile/agile-guide/what-is-minimum-viable-product
Topics
Community Discussion
5B is the right call here. The product owner wanting features released throughout development points straight to MVP, since the whole idea behind a minimum viable product is getting something usable into hands early and often rather than waiting for the full delivery.
Good call on B and the MVP angle, though I'd add that the key giveaway is the continuous feedback loop, not just shipping early, since the product owner wants to refine features based on real user input throughout the process.
B is the right call here. Since the PO wants early releases, defining the MVP lets the team get something valuable out fast instead of waiting the full year.
Confirmed B on exam last week. The product owner wants incremental value delivery, which maps directly to Domain 3 (Business Environment) and the agile principle of frequent, working releases. Facilitating sprint planning with an MVP focus lets the team slice the product into releasable increments rather than waiting a full year. Option A is tempting but velocity measures throughput, not value, so it does not fully address what the PO is asking for.
Agreed on B, and just to add, the MVP focus also gives the PO something tangible to take back to stakeholders for feedback before the team builds further, which is half the point of incremental delivery.