PMP · Question #1378
A project manager is facilitating a project steering committee meeting where the prioritization of work items in the backlog is being discussed. The engineering executive wants to prioritize features
The correct answer is C. Ensure that the team assesses opportunities to deliver the highest business value items. When different executives have conflicting prioritization criteria, the project manager should guide the team to prioritize work items based on delivering the highest business value.
Question
A project manager is facilitating a project steering committee meeting where the prioritization of work items in the backlog is being discussed. The engineering executive wants to prioritize features based on level of effort, completing the smallest items first. The quality executive wants to complete the most complex tasks first to have adequate time to ensure a quality product is delivered. The compliance officer wants to complete items with associated regulatory components as they are essential items. How should the project manager prioritize the work items?
Options
- AEnsure that the project value is within the quality guidelines by prioritizing and completing intricate
- BComplete tasks associated with regulatory components as the team cannot deliver business
- CEnsure that the team assesses opportunities to deliver the highest business value items
- DComplete the smaller tasks first to allow the team opportunities to prototype and evaluate
How the community answered
(51 responses)- A4% (2)
- B16% (8)
- C73% (37)
- D8% (4)
Why each option
When different executives have conflicting prioritization criteria, the project manager should guide the team to prioritize work items based on delivering the highest business value.
Prioritizing intricate tasks for quality alone may delay the delivery of high-value, simpler items or items with critical regulatory importance, failing to align with broader business goals.
While regulatory compliance is critical, it represents one type of business value; focusing solely on regulatory components might neglect other high-value features or user needs that contribute to overall project success.
Prioritizing by highest business value ensures that the project delivers the most critical outcomes aligned with strategic organizational goals, providing a common objective that transcends individual executive preferences and maximizes overall impact.
Prioritizing small tasks first (e.g., 'easy wins') without considering their business value can lead to delivering many low-impact features while critical, high-value items are delayed, diminishing the project's overall impact.
Concept tested: Backlog prioritization by business value
Source: https://learn.microsoft.com/en-us/azure/devops/boards/backlogs/manage-backlogs?view=azure-devops
Topics
Community Discussion
8C is correct. The PMBOK principle is that prioritization should always be driven by value delivery, not by effort or internal preferences. Regulatory items are important, but they still need to be weighed against overall business value. The other options each lock onto a single stakeholder's bias instead of using value as the deciding factor, which is exactly what the exam tests here.
Agreed on C, and the trap I fell into the first time was option D because it sounds like the "safe" answer, but the exam wants you to understand that even compliance items get ranked by value, not treated as automatic top priority.
First leaned B since compliance sounds urgent, but value-based prioritization is the PMP default.
B is right but the exam usually pairs value with sponsor input so watch for that combo in the stem.
C is correct because agile always prioritizes by highest business value first. Which prioritization technique does your org prefer, MoSCoW or WSJF?
C is correct, value drives prioritization. Has anyone seen MoSCoW used effectively on hybrid projects?
Value drives prioritization, sure, but on hybrid projects MoSCoW works best when you treat the Must-haves like the support beams in a house, the load-bearing stuff you cannot ship without, while the Could-haves and Won't-haves flex with each sprint.
Leaned toward B first, but steering committees prioritize by business value, not individual demands.