Your organization is implementing a new customer portal using a hybrid approach. The database migration follows a waterfall methodology with detailed planning, while the user interface development uses Kanban with continuous flow. The project charter specifies a fixed go-live date in four months. During the first retrospective, the UI team identifies that database schema decisions are blocking their work, causing significant wait time. Stakeholders are concerned about meeting the deadline. How should you address this integration challenge?

Question

Accepted Answer

The correct answer is A. Hybrid projects require integration mechanisms that bridge different methodologies without forcing teams to abandon their effective approaches. A cross-functional working group enables rapid decision-making while respecting each team's methodology, reducing wait times and maintaining momentum (ECO Process Task 1.2). This addresses the root cause—the need for synchronized decisions—rather than symptoms. Option C appears structured but would increase wait times and rigidity, worsening the blocking issue. Option D adds bureaucracy that slows decisions rather than enabling flow. Option B is unrealistic and disruptive; forcing methodology changes mid-project typically creates more problems than it solves, and the database work may have valid reasons for its predictive approach.

More Process Questions