4.1. Develop an Integrated Project Management Plan and Plan Delivery
💡 First Principle: An "integrated" plan means every subsidiary plan (scope, schedule, cost, risk, quality) is checked for consistency against the others, not authored in isolation — a schedule that ignores a resourcing constraint documented in the resource plan isn't integrated, it's just two separate documents that happen to share a folder.
Enablers: assess project needs/complexity/magnitude, recommend a development approach (predictive, adaptive/agile, or hybrid), determine critical information requirements (including AI-assisted forecasting where relevant), recommend an execution strategy, create the integrated plan, estimate work effort and resource requirements, assess consolidated plans for dependencies/gaps/continued business value, maintain the plan as conditions change, and collect/analyze data to make informed decisions.
Selecting a development approach is itself a tested decision, not a given: high-uncertainty, evolving-requirements work favors adaptive/agile; well-understood, low-change work favors predictive; most real projects land somewhere in a hybrid blend. The exam expects you to justify the approach based on project characteristics described in the scenario, not apply your organization's default methodology reflexively.
⚠️ Exam Trap: Picking "agile" as the answer whenever a scenario mentions changing requirements, without checking whether the described work also has fixed regulatory deadlines or contractual scope — those characteristics can push the right answer toward hybrid or predictive despite the changing-requirements signal.
Reflection Question: Describe a project where a hybrid approach (not purely predictive or purely agile) was the right call. What specific project characteristics drove that choice?
