PMP · Question #1231
A project manager implementing a hybrid project is dealing with multiple stakeholders in a rapidly changing business environment. How should the project manager ensure that the needs of stakeholders…
The correct answer is B. Use iterative life cycles involving stakeholders to enable the team to improve the product end. To consistently meet stakeholder needs in a rapidly changing hybrid project, the project manager should utilize iterative life cycles that actively involve stakeholders.
Question
Options
- AAdd more iterative techniques to improve stakeholder learning.
- BUse iterative life cycles involving stakeholders to enable the team to improve the product end
- CIdentify all the critical stakeholders during project initiation.
- DAssign one team member to one stakeholder to ensure that the responsible team member is
How the community answered
(66 responses)- A3% (2)
- B76% (50)
- C15% (10)
- D6% (4)
Why each option
To consistently meet stakeholder needs in a rapidly changing hybrid project, the project manager should utilize iterative life cycles that actively involve stakeholders.
Using iterative life cycles that involve stakeholders allows for frequent feedback, review, and adaptation to changing requirements and business environments, ensuring that stakeholder needs are consistently met through ongoing adjustments and product improvement. This approach inherently accommodates rapid change by validating increments with stakeholders.
Assigning one team member to one stakeholder could lead to communication bottlenecks or inconsistencies if not managed carefully, and doesn't inherently guarantee that all changing stakeholder needs are understood and incorporated across the entire project.
Concept tested: Hybrid project management, stakeholder engagement in iterative environments
Source: https://www.pmi.org/pmbok-guide-standards/agile/agile-practice-guide
Topics
Community Discussion
8B is the right call here. The "iterative" plus "involving stakeholders" combo is the giveaway, because in a hybrid environment you need continuous stakeholder feedback loops to adapt to all that rapid change, not just a one-time identification at initiation.
B is correct. In a rapidly changing environment you want stakeholders involved in the iterative cycles so feedback gets folded back into the product before things drift too far.
B is right and Carlos nailed the reasoning, but on the exam watch for the word "frequently" in the stem because the PMBOK frames it as continuous stakeholder engagement through reviews and retrospectives, not just involvement in cycles.
B is the answer here. In a hybrid environment with rapid change, you need iterative cycles that pull stakeholders in so feedback lands before the product drifts. A is close but talks about learning instead of delivering working increments that stakeholders actually validate. D is unscalable and creates single points of failure, and C is a one-time initiation activity that ignores the reality that stakeholders shift in dynamic environments.
Yeah B is right, I picked it on my exam last month, but I would add that the word iterative in the stem is your biggest clue because it basically screams agile before you even read the options.
B is right for hybrid but does iterative always mean stakeholders review each sprint?
B is right for hybrid, but iterative does not automatically mean sprint reviews every cycle; whether stakeholders review each iteration depends on the engagement plan and risk tolerance, so do not conflate the cadence with the methodology.
B is the one. Saw this on my exam last month and the phrase "rapidly changing business environment" was my cue that they wanted iterative delivery with stakeholder involvement, not a one-time identification step. C trips people up because it sounds like solid initiation work, but it doesn't address the ongoing adaptation that a hybrid project in a shifting environment actually demands.