PMP Practice: Create an Integrated Project Management Plan

In agile environments, integrated planning balances stakeholder needs for visibility with the team's ability to respond to change. A release roadmap with high-level themes and value-based outcomes provides the strategic view investors need while respecting the team's constraint that detailed commitments beyond two sprints are unreliable. Using historical velocity data to create probabilistic forecasts for later periods is a legitimate agile planning technique that acknowledges uncertainty while still providing meaningful projections. This approach integrates business needs with adaptive planning principles and uses empirical data to support forecasting. The scenario specifically mentions stabilized velocity over four sprints and consistent throughput, which are the closing facts that make probabilistic forecasting viable and clearly the best approach.

**Why not A:** Creating a fixed-scope six-month plan with milestone dates contradicts the team's legitimate concern about planning beyond two sprints and ignores the technical uncertainty acknowledged in the scenario. Negotiating the team into committing to dates they cannot reliably predict undermines trust and sets unrealistic expectations.

**Why not B:** Escalating the conflict to the executive sponsor treats a planning methodology question as a disagreement requiring arbitration. The project does not need to choose between predictive and agile exclusively; it needs a planning approach that serves both stakeholder needs. This is a facilitation opportunity, not an escalation issue.

**Why not C:** Deferring roadmap planning until after the investor presentation fails to address the immediate business need. The product owner requires a roadmap for the presentation in three weeks, and avoiding the planning challenge does not serve either stakeholders or the team. This approach misses the window to provide meaningful guidance.