Skip to content
PMPMedium

PMP Practice: Examine the business value throughout the project

Question 2 of 4 in Execute Project with the Urgency Required to Deliver Business Value

Pick an answer below — you'll get the explanation instantly, no signup.

Nari Jeong-Tanaka is managing a project for Delightful Chaos Labs to upgrade their entire warehouse management system across 47 distribution centers. The project has a fixed regulatory compliance deadline in 18 months, a detailed scope validated by legal and operations teams, and requires integration with legacy systems that cannot be changed. The implementation sequence must follow a specific order due to data migration dependencies between facilities. During a project review, a team member suggests switching to an iterative approach with two-week sprints to 'deliver value faster' and 'be more agile.' The sponsor is intrigued and asks Nari for her recommendation. What should Nari do?
Show answer & explanation

Correct answer: Recommend maintaining the current predictive approach, explaining that the fixed deadline, regulatory requirements, sequential dependencies, and legacy system constraints make a plan-driven execution most appropriate for delivering the required business value on time

Explanation

This scenario presents a project with characteristics that strongly favor a predictive approach: fixed regulatory deadline, validated and stable scope, sequential dependencies that must follow a specific order, and legacy system integration constraints that cannot be modified. The project manager should recommend maintaining the predictive approach and educate stakeholders on why this methodology best supports delivering business value given these constraints. While iterative approaches offer benefits in the right contexts, applying them to projects with these characteristics would introduce unnecessary risk and complexity without improving value delivery. The key is matching methodology to project context, not defaulting to one approach because it sounds modern or appealing. The PM has already committed to a predictive approach that fits the project's realities, and the sponsor's question provides an opportunity to reinforce why this choice serves the project's success.

**Why not A:** A hybrid approach with two-week sprints for new features does not fit this project's characteristics. The scope is validated and fixed, the implementation sequence is dictated by data migration dependencies, and legacy systems cannot be changed. There are no evolving requirements or adaptive components that would benefit from iterative cycles.

**Why not B:** Transitioning to iterative delivery with two-week release cycles across 47 distribution centers ignores the sequential data migration dependencies between facilities. The centers must be upgraded in a specific order, and breaking this into arbitrary two-week increments would violate the required sequencing and risk data integrity issues.

**Why not D:** Scheduling a collaborative workshop to let the group decide methodology based on preferences treats methodology selection as a democratic choice. The project's constraints—fixed deadline, stable scope, sequential dependencies, and legacy integration—objectively determine the most appropriate approach, and allowing collective preference to override project realities would be irresponsible.

Key Concept

This question covers Examine the business value throughout the project under Execute Project with the Urgency Required to Deliver Business Value (Process).

Share:

This is 1 of 100 free PMP questions

Unlock 6,300+ PMP practice questions with detailed explanations, progress tracking, and exam readiness prediction.

Unlock All Questions