← ECO 2026 tasks

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

II.1 · Last updated: 11/10/2026

Deciding which plan gets written

II.1 — Develop an Integrated Project Management Plan and Plan Delivery opens the Process domain of the 2026 ECO. The domain carries 41% of the exam and holds ten tasks. With nine enablers, this is the second most broadly defined task in the whole outline; only II.5 — Plan and Manage Procurement, with ten, carries more.

Two of the nine begin with the verb "recommend", and that tells you where the weight of the task lies. Before anyone writes a plan, someone has to decide which approach and which strategy the plan will follow, and this task is mostly about that decision.

The old "II.1" was about value delivery

The number II.1 was handed to a new topic in 2026, and its former subject moved one slot down. In 2021, II.1 meant executing the project with the urgency required to deliver business value, a topic that now lives in II.3 — Help Ensure Value-Based Delivery. In 2026, II.1 is the integrated plan and delivery planning, and its closest counterpart in older material is II.13, which asked candidates to determine the appropriate project methodology and methods.

An older question tagged "II.1" is therefore most likely about value delivery. Because the two tasks sit next to each other, the mix-up is easy to overlook. Several other numbers in the Process domain (II.5, II.6, II.8 and II.10) also changed topics, and the full breakdown is in what changed in the 2026 PMP exam.

Gathering the plans and making them agree

PMBOK® 8 ties this work to a process whose definition comes very close to the ECO's own task title. Integrate and Align Project Plans consolidates and aligns the plan components of all the performance domains into a unified project management plan, one that details how the project will be executed, monitored and controlled, and closed (PMBOK® 8, Guide p.16).

Each of the two verbs in that definition carries its own weight. Collecting the components into one document is only half the job. The harder half is alignment, which means making sure the schedule is consistent with the budget and the scope with the resources. The ECO's enabler about assessing consolidated plans for dependencies and gaps describes exactly that half.

The process sits in the Planning focus area of the Governance performance domain (PMBOK® 8, Guide p.9). The Guide adds that alignment with strategic goals becomes concrete here as well, because the activities that will reach those goals are identified and the link is drawn in Integrate and Align Project Plans (PMBOK® 8, Guide p.10).

Choosing an approach along a spectrum

Recommending a development approach, in PMBOK's telling, is not a matter of ticking one of three boxes. The book draws the approaches as a spectrum with predictive at one end, adaptive at the other and hybrid in between, and the way of working becomes increasingly iterative and incremental as you move toward the adaptive end (PMBOK® 8, Standard p.60, Figure 4-2).

The book also says who makes the choice. It is typically the project manager, in consultation with the project management team, who carries out the evaluations needed to set up the framework and way of working based on the nature of the project (PMBOK® 8, Standard p.60). The same page lists the main factors in that choice: the project's requirements, scope, timeline, and goals; the organization's culture and needs; the level of stakeholder involvement; the risk profile; technological considerations; and the overall complexity of the project context.

A list that long explains why "which approach should we use?" cannot be settled on a single factor. On the exam, an option that rests only on "the requirements are unclear" usually falls short. The book frames the predictive case from the other side, too. When requirements are sufficiently clear and stable early in the project, a predictive approach may be the best fit, and the schedule and cost baselines are then set according to the scope to be delivered (PMBOK® 8, Standard p.60).

Hybrid comes in three levels

The book doesn't treat hybrid as one thing. A hybrid development approach combines elements of adaptive and predictive approaches, and it suits situations where there is uncertainty or risk around the requirements. The book's example is the design of a custom home, where it makes sense to iterate on the build no more than once after the design is complete. Hybrid approaches also help when deliverables can be modularized or developed by different teams (PMBOK® 8, Standard p.65). The same page makes a bold claim on top of that, saying that in practice most projects can strongly benefit from a hybrid approach that combines adaptive and predictive methods (PMBOK® 8, Standard p.65).

Drawing on PMI's Disciplined Agile® tool kit, the book then defines three levels of hybrid (PMBOK® 8, Standard p.66). At Level 1 a predictive approach dominates the way of working, and some adaptive elements are used to relieve specific pain points. At Level 2 both approaches contribute significantly to the project's success. At Level 3 an adaptive approach becomes the main contributor, while some predictive elements are kept.

Because of this, "we use a hybrid approach" is not a complete answer on its own. The level at which the hybrid is set up shapes how the plan itself is written.

Execution strategy and the question of who does the work

The most concrete PMBOK counterpart to "recommend a project execution strategy" is a Governance process. Plan Sourcing Strategy is where the team decides whether to use internal or external resources for different parts of the project, weighing factors such as organizational culture, specialized skills, resource capacity, risk, and the overall value proposition (PMBOK® 8, Guide p.16).

Where the process sits is telling, since it belongs to the Planning focus area of the Governance domain (PMBOK® 8, Guide p.9). In PMBOK 8 the make-or-buy decision is pulled forward into governance and taken while the plan is being built, instead of being left as a procurement detail for later. Carrying the decision out is the business of the procurement task.

A plan is maintained after it is approved

Two of the ECO's enablers reach past the moment of approval: assessing consolidated plans for dependencies, gaps and continued business value, and maintaining the integrated plan.

The phrase "continued business value" is the more interesting of the two. A plan is reviewed for internal consistency, and it is also reviewed for whether it still produces value, which connects this task directly to II.3 — Help Ensure Value-Based Delivery. What happens when the plan itself has to change belongs to another task. Once baselines are in place, changes to plan components go through the formal process described in III.3 — Manage and Control Changes.

How much plan is enough

The most common misreading of this task is the assumption that an integrated plan has to be exhaustive. The Guide's view of tailoring points the other way. Projects use "just enough" processes, methods, templates and artifacts to achieve the desired outcomes (PMBOK® 8, Guide p.34), and how much counts as enough depends on the business environment, regulatory requirements, the need for innovation, market conditions, team size, the degree of uncertainty and the complexity of the project.

The same page sets a limit. In organizations with established process governance, tailoring has to stay consistent with the organization's policy and strategy (PMBOK® 8, Guide p.34), so "we streamlined the process" is not a justification by itself.

The way the book describes its own reach supports this flexibility. The standard applies to projects in every sector, including business, government and nonprofit, regardless of geographic region, organizational size or development approach (PMBOK® 8, Standard p.3). Since no single template is expected to fit everyone, the project itself decides how heavy its plan should be.

About the citations

Every page number above refers to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked "ECO" separately.

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

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 describes the book; it does not replace it.

iyzico ile Öde, Visa, MasterCard