Skip to content
PMPMedium

PMP Practice: Participate in agreement negotiations

Question 4 of 4 in Negotiate Project Agreements

Sky Petersen is managing a product development project for Pickle Rocket Labs, a medical device company creating a new patient monitoring system. The project has two major components: hardware manufacturing (highly regulated, fixed scope, 18-month timeline) and software interface development (evolving user requirements, 12-month timeline). Sky is negotiating a contract with Cosmic Solutions, a vendor who will deliver both components. The vendor's proposal suggests using a fixed-price contract for the entire project to simplify procurement. However, during negotiation discussions, the vendor's technical lead mentions they've never built medical device software before and expects significant learning as they understand clinician workflows. The hardware specifications are fully defined and pre-approved by regulatory authorities. What approach should Sky negotiate to best meet the project's objectives?
Show answer & explanation

Correct answer: Negotiate a hybrid contract structure: fixed-price for hardware manufacturing and time-and-materials with not-to-exceed caps for software development

Explanation

A hybrid contract structure aligns the procurement approach with each component's characteristics and risk profile. The hardware has fixed scope, clear requirements, and regulatory approval—making fixed-price appropriate and low-risk. The software faces significant uncertainty due to evolving requirements and the vendor's learning curve with medical workflows, making time-and-materials with spending caps appropriate to accommodate necessary changes while controlling costs. This hybrid approach directly addresses the scenario's stated constraint that the vendor expects significant learning during software development. By matching contract type to component risk, Sky protects the project from both over-rigid constraints on uncertain work and unlimited cost exposure. The negotiation meets project objectives by enabling predictable hardware delivery while allowing adaptive software development within controlled boundaries.

**Why not A:** Requesting a purely agile contract for both components ignores the hardware's characteristics. The hardware specifications are fully defined and pre-approved by regulatory authorities, making a fixed-price contract appropriate for that component. An agile contract for well-defined regulated hardware adds unnecessary complexity and cost uncertainty.

**Why not B:** Accepting the fixed-price proposal for the entire project exposes the organization to significant risk on the software component. The vendor has never built medical device software and expects significant learning, making fixed-price inappropriate since scope changes will be inevitable and penalty clauses would create adversarial dynamics during the learning process.

**Why not D:** Rejecting the vendor entirely and seeking a replacement with medical device software experience eliminates the best technical fit for the hardware component. Rather than discarding a strong vendor because of one component's uncertainty, a hybrid contract structure can address both components' risk profiles appropriately.

Key Concept

This question covers Participate in agreement negotiations under Negotiate Project Agreements (People).

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