---
reference_type: Performance Domain
reference_id: PD8-03
name: Schedule
version: "1.0.0"
status: Active
edition: PMBOK8
pmbok8_source: "PMBOK8 Guide §2.3 — Schedule Performance Domain"
authority: PMI-derived
file_path: "reference/performance-domains/PD8-03-schedule.md"
last_updated: "2026-06-07"
---

# PD8-03 — Schedule Performance Domain
**Type:** Performance Domain  
**Edition:** PMBOK 8th Edition (2025)  
**PMBOK 8 Source:** PMBOK8 Guide §2.3 — Schedule Performance Domain  
**Version:** 1.0.0  

## Definition
The **Schedule Performance Domain** addresses activities and processes required to oversee the project's timely completion (PMBOK8 §2.3). Project scheduling provides a plan representing how and when the project will deliver the products, services, and results defined in the project scope. The schedule serves as a tool for communication, managing stakeholder expectations, and providing a basis for performance reporting.

## Desired Outcomes
Per PMBOK8 §2.3, effective execution of the Schedule Performance Domain results in:
- **Scheduling approaches** that are consistent with the development approach selected (predictive, adaptive, or hybrid).
- **A project life cycle** consisting of phases that connect the delivery of business and stakeholder value from the beginning to the end.
- **A holistic approach** to delivering project outcomes with no gaps or areas of misalignment.
- **Complete schedule documentation** that includes dependencies, durations, resource allocations, and milestones.
- **Timely identification** of potential delays and risks, enabling proactive corrective actions to keep the project on track.

## Key Processes and Activities
This domain encompasses the following 3 canonical processes (PMBOK8 §2.3.2):
1. **Plan Schedule Management** (§2.3.2.1) — Establishes the policies, procedures, and documentation for planning, developing, managing, executing, and controlling the project schedule.
2. **Develop Schedule** (§2.3.2.2) — Analyzes activity sequences, durations, resource requirements, and schedule constraints to create the project schedule model.
3. **Monitor and Control Schedule** (§2.3.2.3) — Monitors the status of the project schedule, tracks actual progress against the baseline, and manages changes to the schedule model.

## Relationship to Principles
| Principle | Connection |
|---|---|
| P8-01 — Holistic View | Scheduling must account for resource availability, risk buffers, and cross-project/portfolio dependencies (§2.3, §3.3.3). |
| P8-02 — Focus on Value | Schedules should be structured to enable progressive value realization (e.g., release planning) and avoid delays that erode ROI (§3.4.3). |
| P8-03 — Embed Quality | Prioritizes complete and correct scheduling practices and integrates quality gate reviews as scheduled milestones (§3.5.3). |

## Artifact Connections
| Artifact | Connection |
|---|---|
| A15 — Schedule Baseline | The approved schedule model used as a benchmark to measure actual progress and schedule variance. |
| A11 — Responsibility Assignment Matrix (RACI) | Defines who is responsible for schedule activities, ensuring tasks have clear owners. |
| A17 — Performance Reporting Record | Tracks schedule variance (SV) and schedule performance index (SPI) to report performance. |

## Skill Connections
| Skill ID | Skill Name | Connection |
|---|---|---|
| SKL-03-05 | Plan Schedule Management | Defines the scheduling tools, methods, and variance thresholds for the project. |
| SKL-03-06b | Develop Schedule | Performs activity sequencing, duration estimation, and critical path analysis to build the schedule. |
| SKL-05-04 | Monitor and Control Schedule | Tracks schedule status, manages variances, and implements corrective actions or schedule changes. |

## Questions to Ask in Practice
1. Is our scheduling approach aligned with the delivery cadence and development approach of our deliverables?
2. Have we built in sufficient buffers for known-unknown risks to protect our target completion dates?
3. How frequently are we reviewing the critical path to anticipate and prevent schedule slippages?
4. Are schedule commitments co-created with the team members who will actually execute the work?

*Authority: PMBOK8 Guide §2.3 — Schedule Performance Domain · Source type: PMI-derived*
*Repository: https://github.com/fakhruldeen/PMOSkills*
