PMP · Question #909
A project manager has been newly assigned to an existing project. The project manager noted that the input from a business unit, which is critical to the success of the project, was not included in…
The correct answer is C. Optimize alignment among needs, expectations, and project objectives. The project manager observes critical business unit input missing, leading to complaints about operational results and misalignment. The most comprehensive action is to optimize alignment among the business unit's needs, expectations, and the project's objectives to ensure…
Question
A project manager has been newly assigned to an existing project. The project manager noted that the input from a business unit, which is critical to the success of the project, was not included in any project assets. Instead, there were many complaints about the project's operational results and the alignment with solutions affected by the business unit's operations. What action should the project manager take?
Options
- AValidate that the project requirements information is up-to-date.
- BDetermine the degree to which the project is in compliance.
- COptimize alignment among needs, expectations, and project objectives.
- DDetermine a strategy for change responses to new objective requests.
How the community answered
(53 responses)- A11% (6)
- B4% (2)
- C70% (37)
- D15% (8)
Why each option
The project manager observes critical business unit input missing, leading to complaints about operational results and misalignment. The most comprehensive action is to optimize alignment among the business unit's needs, expectations, and the project's objectives to ensure success.
While validating requirements is important, it's a component of addressing the broader misalignment issue, not the primary strategic action to optimize overall project alignment with business needs.
Determining compliance is a verification step, but it doesn't address the root cause of missing critical input or proactively realign the project with the business unit's actual needs and expectations.
The core problem described is a fundamental misalignment: a critical business unit's input was omitted, resulting in complaints about the project's operational results and its solutions not aligning with the business unit's operations. The most overarching and strategic action is to actively work to optimize the alignment between what the business unit *needs*, what they *expect*, and what the project is *objectively* aiming to achieve. This involves re-engaging the business unit, understanding their requirements, and adjusting the project's direction to ensure it delivers solutions that truly meet their operational demands and strategic goals.
Developing a strategy for change responses is reactive; the immediate problem is a current misalignment and lack of critical input, which needs proactive reconciliation, not just a plan for future requests.
Concept tested: Stakeholder engagement and project alignment with business objectives
Topics
Community Discussion
5C is correct. The key phrase is alignment with solutions affected by the business unit, which points directly to optimizing alignment among needs, expectations, and project objectives. A is wrong because the issue is not outdated requirements, it is that the business unit was never engaged in the first place. The PM needs to bring that missing stakeholder input into the fold and realign objectives, which is exactly what C describes.
Sat for this last month and C is the right call. The stem is really just testing whether you catch that a missing stakeholder means you need to revisit alignment, not compliance or requirements. One thing that tripped me up in practice, though: does anyone know if PMP always treats alignment as the answer when the scenario involves a gap in stakeholder engagement, or are there cases where they want you to go straight to updating the requirements documentation first?
Yeah C is right, but to answer your question: PMI usually wants you to fix alignment first when a stakeholder is missing entirely, whereas requirements doc updates come into play when the stakeholder was engaged but gave you incomplete or conflicting info.
Yeah C is right. You gotta get that business unit aligned with project objectives ASAP.
C is right but the exam usually wants stakeholder engagement plan referenced as the mechanism, not just generic alignment.