PMP Practice: Analyze the bounds of the negotiations for agreement

This scenario tests the project manager's ability to negotiate agreements by finding creative solutions that address the core concerns of both parties rather than accepting a binary win-lose outcome. The hospital's fundamental need is HIPAA-compliant security for patient data, not necessarily a blanket review of all features. The startup's core need is maintaining iterative delivery to satisfy investors, not avoiding all security review. Option A addresses both concerns through differentiated treatment: features handling sensitive patient data get full certification (satisfying compliance requirements), while other features maintain agile cadence (preserving investor confidence through visible progress). Involving the hospital's security team in sprint planning creates collaborative visibility and may identify features that need certification earlier, avoiding surprises. This represents effective negotiation by understanding interests rather than positions, a key skill when participating in agreement negotiations. The solution maintains the agile approach where it matters most while accommodating legitimate regulatory requirements where necessary.

**Why not B:** While accepting the terms and restructuring the roadmap is pragmatic, it fails to negotiate effectively. The product owner has explicitly stated that a six-month delay would cause investor withdrawal, making this approach likely to fail regardless of how the roadmap is restructured. Additionally, a skilled negotiator should explore creative alternatives before simply accepting terms that create known major problems. This represents a compromise that may satisfy the hospital but doesn't adequately address the startup's investor concerns, which were clearly stated as a deal-breaker.

**Why not C:** This represents failure to negotiate and an all-or-nothing approach. The project manager's role includes finding solutions that balance competing needs, not declaring one party's requirements non-negotiable and walking away. The hospital partnership offers significant value (funding and real patient data), and declining it without exploring creative alternatives fails to serve the project's interests. Additionally, declaring 'the agile approach is non-negotiable' misunderstands agile principles—agile values responding to change and collaboration, which includes adapting practices to work within necessary constraints like regulatory compliance.

**Why not D:** Escalation is premature because the project manager has not yet attempted to negotiate a creative solution. While the scenario involves competing requirements, there is no indication that the gap is genuinely beyond the PM's ability to facilitate a solution. Escalating immediately sidesteps the PM's responsibility to negotiate agreements and find collaborative solutions. Effective project managers explore options and propose alternatives before escalating. The scenario provides enough information and authority for the PM to suggest a differentiated approach that addresses both parties' core needs without executive intervention.