Your organization is implementing a hybrid project to modernize its payment processing system. The core payment engine follows a waterfall approach with strict regulatory requirements and formal testing gates, while the mobile app interface is developed using Scrum with two-week sprints. You are currently planning the integration testing phase. The payment engine team requests a four-week notice before any integration point, while the Scrum team wants to integrate continuously as features are completed. How should you handle this conflict in integration approaches?

Question

Accepted Answer

The correct answer is B. Hybrid projects require integration mechanisms that honor the constraints of both approaches while maximizing value delivery. Option B creates a structured approach that provides the predictive team with needed stability through scheduled integration windows while still allowing more frequent integration than pure waterfall would permit, thus partially satisfying the adaptive team's need for feedback. Option C is the main distractor and while technically sound for allowing parallel work, it defers the actual integration testing and doesn't resolve the fundamental conflict about when real integration occurs—stubs can mask integration issues until very late. Option A forces the adaptive team into a waterfall cadence, negating hybrid benefits, while Option D inappropriately escalates a tactical issue that the project manager should resolve.

PMP Practice Question: Process — Hybrid, Medium

More Process Questions