← ECO 2026 tasks

II.8 — Plan and Manage Schedule

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

The schedule comes after the approach

II.8 — Plan and Manage Schedule is the eighth task in the Process domain of the 2026 ECO, a domain that carries 41% of the exam. The ECO lists eight enablers for it:

The condition in the first item sets the logic of the whole task. A schedule is prepared once the development approach has been chosen, and it is shaped by that approach. The third item points the same way, since it puts story points next to milestones and dependencies. Nothing in the task assumes a single scheduling method.

Scope and schedule traded numbers

II.8 sits at one end of the two-way number swaps in the 2026 ECO. In 2021, II.8 was scope, and that topic now lives in II.2 — Develop and Manage Project Scope. In 2026, II.8 is the schedule, which was II.6 in 2021, and the number II.6 has meanwhile gone to finance.

A question tagged "II.8" can therefore be about scope or about the schedule, depending on which ECO it was tagged against. Both tasks sit in the Process domain and both follow the "plan and manage" naming pattern, which hides the mismatch well. The chain actually has three links, because the old II.8 went to the new II.2, the old II.6 went to the new II.8, and the new II.6 covers a different subject altogether. Map by title. The full picture is in what changed in the 2026 PMP exam.

Three processes in the Schedule domain

PMBOK® 8 gives this subject a performance domain with only three processes (PMBOK® 8, Guide pp.48-49, Figure 2-20). Plan Schedule Management establishes the policies, procedures, and documentation for designing, developing, managing, performing, and maintaining the schedule, and the benefit the book names is guidance and direction on how the schedule will be managed throughout the project. Develop Schedule analyzes sequences, durations, resource requirements, and schedule constraints to create a schedule model for executing, monitoring, and controlling the project. Monitor and Control Schedule tracks the status of the project to update the schedule and manages changes to the schedule baseline or agreed-upon schedule.

Sequencing activities and estimating their durations are no longer separate processes in PMBOK 8, since both now sit inside the definition of Develop Schedule. The phrase "or agreed-upon schedule" in the third definition also deserves attention, because it accepts that not every project will have a formal schedule baseline.

Predictive and adaptive tools in the same process

The ECO's first enabler refers to the development approach, and the book's tool lists show the connection plainly. The tools of Develop Schedule include schedule compression, the critical path method, the critical chain method, resource leveling under the heading of resource optimization, and agile release planning, all in one list (PMBOK® 8, Guide p.50).

On the Monitor and Control Schedule side the mix is even broader (PMBOK® 8, Guide p.54). Under data analysis it lists earned value analysis, burnup and burndown charts, performance reviews, trend analysis, variance analysis, and what-if scenarios. Next to these come the critical path and critical chain methods, leads and lags, schedule compression, branch and bound, velocity, daily coordination meetings, sprint reviews, and backlog refinement.

So PMBOK puts predictive and adaptive scheduling tools side by side inside the same process. An answer option claiming that agile projects have no schedule is wrong for that reason, since an agile project has a schedule too, only in a different form. The book also explains the adaptive logic. Because features represent the value the customer expects, a timeline showing which features will be available at the end of each iteration gives a project schedule that is easier to understand (PMBOK® 8, Guide p.146).

Resource leveling before the baseline

The ECO treats baselining the schedule as an enabler of its own, and the book sets a condition ahead of that step (PMBOK® 8, Guide p.53). The draft schedule is analyzed to find conflicts in its logical relationships and to decide whether resource leveling is needed before it is approved and used as a baseline. At the same time, having a draft schedule in hand makes it easier and more accurate to estimate the labor and physical resources needed to reach the project objectives, and those estimates can in turn affect whether the draft is acceptable and call for further adjustments.

The relationship works in both directions, with the schedule shaping resource needs and the resources shaping the schedule. The resource side is covered in II.4 — Plan and Manage Resources. The process outputs list the schedule baseline, the project schedule, schedule data, and project calendars separately (PMBOK® 8, Guide p.50), and the exam expects you to know that these are four different documents.

Schedule variance reaches the budget

The ECO's last enabler belongs to monitoring, and its counterpart is visible in the outputs of Monitor and Control Schedule, which are work performance information and schedule forecasts. The plan updates it lists include the schedule management plan and the schedule baseline, and they also include the cost baseline and the performance measurement baseline (PMBOK® 8, Guide p.54).

That list has an important consequence for the exam. An approved change that moves the schedule often moves cost as well, because the performance measurement baseline combines the scope, schedule, and cost baselines, and when one of them changes the whole is affected. The formal route for such a change is described in III.3 — Manage and Control Changes.

How known risks enter the schedule

The book closes the Schedule domain with a table of outcomes to check, and one of those checks says directly how uncertainty should be reflected in the schedule. Major project constraints and known risks should be factored into the schedule through sufficient float, contingency reserves, or alternate activity network strategies such as secondary plans (PMBOK® 8, Guide p.58). The same table also lists having sufficient buffers built in for known-unknowns.

Seen this way, a buffer in the schedule stops being an arbitrary margin and becomes a form of risk response. The risk side is covered in III.5 — Plan and Manage Risk.

A schedule has to fit the world outside the project

The ECO's second enabler asks for something that is easy to overlook. A schedule that is consistent within itself is not enough, because it also has to fit the work happening outside the project. The Standard says ongoing operations lie outside the scope of a project, yet the two have points where they intersect (PMBOK® 8, Standard p.9). The book places those points in the development of a new product or service, in the improvement of product or service delivery, at the end of the product life cycle, and at each closeout phase or iteration. Each of them needs a place in the schedule.

Dependence on other projects follows the same logic. The book lists reliance on other projects, departments, or functions for decisions, components, or resources as one of the factors to weigh when choosing how to deliver the project (PMBOK® 8, Standard p.68). If the handover date to operations, the date a shared resource will be freed by another project, or a supplier's delivery dates are missing from the schedule, the project can finish on time by its own calendar and still not be ready for use.

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