Develop the Integrated Project Management Plan and Plan Delivery

Integration is the "glue" domain — the PM plan is not one document but a set of subsidiary plans (scope, schedule, cost, quality, resource, communications, risk, procurement, stakeholder) that must be internally consistent. A change to one almost always ripples into another; PMI tests whether you catch that ripple rather than treating each plan in isolation.

Choosing a development approach is now squarely in scope: predictive (plan-driven, sequential), agile/adaptive (iterative, embracing change), and hybrid (mixed, e.g. predictive hardware delivery with agile software sprints). The right choice depends on requirements clarity, risk, regulatory constraints, and stakeholder availability — not personal preference or "what we did last time."

Study focus: tailoring is a named competency — PMI expects you to adjust process rigor to project size and risk rather than always applying the full toolkit.