PMP · Question #21
In the initiating phase of a project, the project manager and team members are prioritizing the product backlog along with the product owner. What should the project manager do next?
The correct answer is B. Produce a value-added product for the customer as continuously as possible.. After prioritizing the product backlog in the initiating phase, the project manager should focus on delivering value to the customer as continuously as possible. This aligns with agile principles of frequent delivery and early value realization.
Question
Options
- AProduce a value-added product for the customer in each phase of the project.
- BProduce a value-added product for the customer as continuously as possible.
- CProduce a value-added product for the customer in the beginning of the project.
- DProduce a value-added product along with the supporting documentation.
How the community answered
(19 responses)- B84% (16)
- C11% (2)
- D5% (1)
Why each option
After prioritizing the product backlog in the initiating phase, the project manager should focus on delivering value to the customer as continuously as possible. This aligns with agile principles of frequent delivery and early value realization.
Delivering value 'in each phase' is too restrictive and does not fully capture the continuous nature of value delivery in agile; value should be delivered more frequently than just phase-by-phase.
In agile project management, after backlog prioritization, the focus shifts to delivering value iteratively and incrementally. Producing a value-added product as continuously as possible allows for early feedback, adaptive planning, and ensures that customers receive usable functionality throughout the project lifecycle, maximizing business value.
Delivering value only 'in the beginning' is insufficient as it ignores the ongoing need for continuous value delivery and feedback throughout the project.
While supporting documentation is important, the primary focus after backlog prioritization in an agile context is the delivery of the product itself, with documentation being a secondary output.
Concept tested: Agile value delivery and continuous integration
Source: https://agilemanifesto.org/principles.html
Topics
Community Discussion
6B is your pick. Think C for Continuously: in Agile, once that backlog is prioritized, you deliver value as continuously as possible, not just phase by phase.
Good call on B but the real driver is shorter feedback loops, continuous delivery is just the mechanism that gets you there.
B is correct. Backlog prioritization with the PO is an adaptive giveaway, and in agile you deliver value continuously through iterations rather than batching it into phases or waiting for documentation.
Agreed on B, but watch out for a drag-and-drop variant of this one where they swap in "sprint planning" instead of "backlog prioritization" and people panic-pick that even though the PO collaboration angle is still the real tell.
Going with D here. The backlog prioritization in initiating sets up delivery, and producing the value-added product along with supporting documentation is what makes the work actually usable and complete for the customer.
B is correct here, Bao, because the question is asking about closing, not delivering. Think CRAFT for closing: Confirm acceptance, Release resources, Archive docs, Formalize sign-off, Transition ownership. Backlog prioritization is an initiating activity, and while producing the product sounds great, it is execution work, not the wrap-up party.