II.8 — Plan and Manage Schedule

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

Where this task sits

II.8 — Plan and Manage Schedule is the eighth task in the Process domain of the 2026 ECO. The domain carries 41% of the exam.

It has eight enablers:

• Prepare a schedule based on the selected development approach
• Coordinate with other projects and operations
• Estimate project tasks (milestones, dependencies, story points)
• Utilize benchmarks and historical data
• Create a project schedule
• Baseline a project schedule
• Execute a schedule management plan
• Analyze schedule variation

The condition in the first enabler is decisive: the schedule is prepared after the development approach is chosen. Story points being named outright in the third points the same way — this task does not assume one scheduling method.

🔴 Do not trust the number

II.8 is one end of the cleanest two-way number swap in the 2026 ECO:

• In 2021, II.8 was scope. In 2026 that topic is II.2 — Develop and Manage Project Scope.
• In 2026, II.8 is schedule. This topic was II.6 in 2021 — and in 2026 the number II.6 went to finance.

So a question tagged "II.8" may be about scope or about schedule depending on which outline it was tagged against. Both sit in the Process domain and both follow the "plan and manage" pattern, which is why the mismatch slips past.

The chain has three links: old II.8 → new II.2, old II.6 → new II.8, and new II.6 is a different subject entirely. Match on the title, never the number; for the general shape of the trap, see what changed in the 2026 PMP exam.

The Schedule domain carries only three processes

PMBOK® 8's performance domain for this subject is strikingly lean (PMBOK® 8, Guide p.48 — Figure 2-20):

• Plan Schedule Management — the process of establishing policies, procedures, and documentation for designing, developing, managing, performing, and maintaining the schedule. Its key benefit is providing guidance and direction on how the project schedule will be managed throughout the project (PMBOK® 8, Guide p.49).
• Develop Schedule — the process of analyzing sequences, durations, resource requirements, and schedule constraints to create a schedule model for project execution and monitoring and controlling (PMBOK® 8, Guide p.49).
• Monitor and Control Schedule — the process of monitoring the status of the project to update the project schedule, and managing changes to the schedule baseline or agreed-upon schedule (PMBOK® 8, Guide p.49).

In older editions, defining activities, sequencing them, and estimating durations were separate processes; the eighth edition folds them all into Develop Schedule. The phrase "or agreed-upon schedule" in the third definition matters too: not every project has a formal schedule baseline.

The approach determines the schedule

The ECO's first enabler refers to the development approach, and the book's tool lists bear that out.

Among the tools of Develop Schedule, the Guide lists schedule network analysis, schedule compression, critical path method, critical chain method, resource optimization (resource leveling) and agile release planning side by side (PMBOK® 8, Guide p.50).

On the Monitor and Control Schedule side the list is even more mixed: critical chain method, resource optimization, leads and lags, schedule compression, branch and bound, velocity, daily coordination meetings, sprint reviews, and backlog refinement (PMBOK® 8, Guide p.54).

So PMBOK places predictive and adaptive scheduling tools inside the same process. Translated for the exam: the option claiming "agile projects have no schedule" is wrong — there is a schedule, its form differs.

The book explains the adaptive logic separately: since features represent expected value to the customer, a timeline that defines which features will be available at the end of each iteration provides a more easily understood project schedule (PMBOK® 8, Guide p.146).

Before baselining: resource leveling

The ECO carries "baseline a project schedule" as its own enabler. The book puts a condition ahead of that step.

The draft schedule is analyzed to identify conflicts with logical relationships and to determine whether resource leveling is required before the schedule is approved and used as a baseline. Conversely, with a draft schedule in hand it is easier and more accurate to estimate the labor and physical resources required to complete the project objectives; those estimates may influence whether the draft schedule is acceptable and may require further adjustment (PMBOK® 8, Guide p.53).

The relationship runs both ways: the schedule shapes resources and resources shape the schedule. For the resource side, see II.4 — Plan and Manage Resources.

The process outputs include the schedule baseline, project schedule, schedule data, and project calendars (PMBOK® 8, Guide p.50) — four separate things, and the exam distinguishes them.

Analyzing schedule variation

The ECO's last enabler is on the monitoring side, and its counterpart shows up in the process outputs.

The outputs of Monitor and Control Schedule are work performance information and schedule forecasts. Among the plan updates it lists not only the schedule management plan and schedule baseline but also the cost baseline and the performance measurement baseline (PMBOK® 8, Guide p.54).

That list carries an important exam consequence: an approved change that moves the schedule usually moves the cost side too. The performance measurement baseline is the combination of the scope, schedule, and cost baselines; when one changes, the whole is affected. For the formal route, see III.3 — Manage and Control Changes.

How uncertainty is absorbed in the schedule

The book says outright how known risks get built into the schedule: constraints and known risks are factored into the project schedule by providing sufficient floats, contingency reserves, or alternate activity network strategies such as secondary plans (PMBOK® 8, Guide p.58).

So buffer in a schedule is not an arbitrary margin but a form of risk response. For the risk side, see III.5 — Plan and Manage Risk.

Coordinating with other projects and operations

The ECO's second enabler points at something most material skips: a schedule is not only internally consistent, it is coordinated with what lies outside the project.

Its counterpart shows up in PMBOK even on the quality side: embedding quality into the schedule includes ensuring scheduling practices and artifacts are reviewed for completeness and correctness, and integrating product quality reviews as scheduled milestones (PMBOK® 8, Standard p.46).

The schedule, in other words, is a document that absorbs other tasks' work. When quality reviews, procurement delivery dates, and handover points to operations find no place in it, the project can finish "on time" and still be undeliverable.

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.