PMP Practice: Identify Value Components with Stakeholders

Value-based delivery means selecting the delivery approach that actually maximizes value given the project's specific constraints and context. This pharmaceutical system has fixed regulatory requirements, locked specifications requiring external approval to change, critical integration dependencies already 60% complete, and a hard deadline tied to clinical trials. These characteristics make a plan-driven approach not just appropriate but necessary — switching to iterative releases mid-stream would introduce regulatory risk, disrupt already-completed integration work, and potentially jeopardize the clinical trial start date. The stakeholders' concern about feedback and value visibility is legitimate, but can be addressed within the existing governance structure through demonstrations and structured reviews. This allows them to verify the work delivers expected value without abandoning an approach that fits the project's constraints. The PM's role includes educating stakeholders on why methodology choices matter and protecting the project from changes that sound good in theory but would harm value delivery in practice.

**Why not A:** Transitioning to agile with bi-weekly sprints would disrupt 60% of completed integration work following the approved technical design. The project has fixed regulatory requirements, locked specifications requiring external regulator approval to change, and a hard deadline tied to clinical trials. Switching methodologies mid-stream introduces significant risk without addressing the stakeholders' underlying concern about visibility.

**Why not B:** Escalating to the project sponsor and compliance officer to determine whether regulatory approval can be obtained for changing the delivery approach adds unnecessary delay. The project characteristics clearly indicate a plan-driven approach is appropriate, and the stakeholders' feedback concern can be addressed within the existing governance framework through demonstrations.

**Why not D:** A hybrid approach where enhancements are handled through an agile backlog introduces methodology complexity that is unnecessary and risky in this context. The project scope is fixed by regulatory requirements, and scope changes require formal external review. Creating a separate agile track for enhancements could blur the boundaries of the regulated scope and create governance confusion.