II.1 — Develop an Integrated Project Management Plan and Plan Delivery

II.1 · Last updated: 24/08/2026

Where this task sits

II.1 — Develop an Integrated Project Management Plan and Plan Delivery is the first task in the Process domain of the 2026 ECO. The domain carries 41% of the exam across ten tasks.

It is the most enabler-heavy task in the entire ECO — nine of them:

• Assess project needs, complexity, and magnitude
• Recommend a project management development approach (predictive, adaptive/agile, or hybrid)
• Determine critical information requirements (e.g., sustainability)
• Recommend a project execution strategy
• Create an integrated project management plan
• Estimate work effort and resource requirements
• Assess consolidated project plans for dependencies, gaps, and continued business value
• Maintain the integrated project management plan
• Collect and analyze data to make informed project decisions

Two of the nine start with the verb "recommend." This task is not about writing the plan — it is about deciding which plan gets written.

🔴 Do not trust the number

The number II.1 changed hands in 2026, and its old meaning moved to the task right next door:

• In 2021, II.1 was executing the project with the urgency required to deliver business value. In 2026 that topic is II.3.
• In 2026, II.1 is the integrated plan and delivery planning. Its closest 2021 counterpart was II.13 (determine appropriate project methodology/methods).

So an older question tagged "II.1" is most likely about value delivery, not about this page's subject. Because the two tasks sit side by side, the confusion is easy to miss.

Within the same domain, the numbers II.5, II.6, II.8, and II.10 also moved to different topics. Match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.

What the integrated plan is

PMBOK® 8 ties this work to a process whose definition nearly matches the ECO task title word for word.

Integrate and Align Project Plans is the process of consolidating and aligning all of the performance domains' plan components into a unified project management plan that details how the project will be executed, monitored and controlled, and closed (PMBOK® 8, Guide p.16).

The two verbs inside that definition matter separately: consolidating and aligning. Gathering the components into one document is not enough; they have to be consistent with each other. The ECO's "assess for dependencies and gaps" enabler is exactly the aligning half.

The process sits in the Planning focus area of the Governance performance domain (PMBOK® 8, Guide p.9). The Guide notes that strategic alignment is depicted in this process too: activities should be identified to enable the goals, and that alignment is illustrated in the Integrate and Align Project Plans process (PMBOK® 8, Guide p.10).

Approach selection happens on a spectrum

The ECO's "recommend a development approach" enabler is not a three-box choice in PMBOK — it is a continuum.

The book draws the approaches as a spectrum running from predictive to adaptive, with hybrid in the middle, becoming increasingly iterative and incremental toward the right (PMBOK® 8, Standard p.60 — Figure 4-2).

Who makes the call is written down too: the choice of development approach is typically made by the project manager in consultation with the project management team, who carries out the necessary evaluations for establishing the framework and way of working based on the nature of the project (PMBOK® 8, Standard p.60).

The main factors are enumerated as well: the project's requirements, scope, timeline, and goals; the organization's culture and needs; the level of stakeholder involvement, risk profile, technological considerations, and the overall complexity of the broader project context (PMBOK® 8, Standard p.60).

Translated for the exam: the answer to "which approach should we use" never rests on a single factor. An option that only says "requirements are unclear" is incomplete; a predictive approach fits when requirements are sufficiently clear and stable early in the project (PMBOK® 8, Standard p.60).

Hybrid is not one thing — it has three levels

Here is the detail most material skips.

A hybrid development approach is a combination of adaptive and predictive approaches, incorporating some elements from each. It may be appropriate when there is uncertainty or risk around the requirements — the book's example is the design of a custom home: once the design is complete, it makes sense to iterate no more than once for the build. Hybrid approaches are also useful when deliverables can be modularized (PMBOK® 8, Standard p.65).

The book then draws on the PMI Disciplined Agile® tool kit to define three levels of hybrid (PMBOK® 8, Standard p.66):

• Hybrid Level 1 — A predictive approach is the dominant contributor to the way of working, while some adaptive elements are leveraged to reduce specific pain points.
• Hybrid Level 2 — Both the predictive and adaptive approaches contribute significantly to the project's success.
• Hybrid Level 3 — An adaptive approach becomes the major contributor to the way of working, with some predictive elements retained.

That trio makes "we use hybrid" insufficient as an exam answer on its own: which level of hybrid determines how the plan gets built.

Sourcing strategy: PMBOK® 8's new process

The most concrete PMBOK counterpart to the ECO's "recommend a project execution strategy" enabler is a process the eighth edition added to the Governance domain.

Plan Sourcing Strategy is the process of deciding whether to use internal or external resources for different parts of a project, considering factors such as organizational culture, specialized skills, resource capacity, risk, and the overall value proposition (PMBOK® 8, Guide p.16).

This process also sits in the Planning focus area of the Governance domain (PMBOK® 8, Guide p.9) — meaning the "make or buy" decision is not a procurement detail in PMBOK 8 but a governance decision made while the plan is being built.

Maintaining the plan is as much the task as building it

The ECO folds the aftermath of the plan into the task through two separate enablers: assess consolidated plans for dependencies, gaps, and continued business value, and maintain the integrated plan.

"Continued business value" is a striking phrase: the plan is reviewed not only for consistency but for whether it still produces value. That means the plan is not a document approved once and shelved — and it ties this task directly to II.3 — Help Ensure Value-Based Delivery.

What happens when the plan itself changes belongs to another task: once baselines are established, changes to plan components go through a formal process — see III.3 — Manage and Control Changes.

How much plan is enough

Finally, the most misread part of this task: the integrated plan does not have to be comprehensive.

The Guide's tailoring principle is short: use "just enough" processes, methods, templates, and artifacts to achieve the desired outcomes. The factors that determine how much is enough include the business environment, regulatory requirements, need for innovation, market conditions, team size, degree of uncertainty, and project complexity (PMBOK® 8, Guide p.34).

The same page adds a caveat: in organizations with established process governance, tailoring should stay aligned with organizational expectations (PMBOK® 8, Guide p.34). "We simplified it" is not a defense on its own.

The book describes its own scope the same way: the standard applies regardless of business, government, or nonprofit sector; geographic region; organizational size; or development approach (PMBOK® 8, Standard p.3).

About the citations

The page numbers above refer to the PMBOK® Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked as "ECO."

⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:

• The Standard for Project Management — cited as Standard p.X
• A Guide to the Project Management Body of Knowledge — cited as Guide p.X

This page cites both books; which number belongs to which book is stated in every citation. The numbers are the books' printed page numbers.

This page explains the book; it does not replace it.