Your organization is executing a hybrid project to modernize its supply chain platform. The backend API development follows Scrum methodology, while hardware procurement and installation follow a predictive approach with fixed milestones tied to vendor contracts. You've established a cadence where API sprints are two weeks, and you conduct integrated planning every six weeks. During the third integrated planning session, the product owner requests prioritizing new API features that require hardware capabilities not included in the current procurement contract. The hardware lead indicates that modifying the contract will take 8-10 weeks and increase costs by 15%. The product owner argues these features are critical for competitive advantage. How should you proceed?

Question

Accepted Answer

The correct answer is A. This scenario involves a significant scope, schedule, and cost decision that crosses the boundary between adaptive and predictive components of the hybrid project. The appropriate response is to perform a thorough cost-benefit analysis that quantifies the business value against the impacts, then escalate to the governance board for an informed decision (ECO Process Task 2.7: Plan and manage budget and resources; Process Task 1.2: Manage communications). Option D is the main distractor because while it appears proactive, it commits resources and vendor negotiations without proper authorization for a change that significantly impacts the baseline. Starting development in parallel before approval creates waste if the decision is not to proceed, and negotiating contract changes without governance approval exceeds typical project manager authority. The hard aspect is recognizing that hybrid projects still require formal change control when modifications cross planning boundaries and significantly impact constraints.

More Process Questions