---
ref_id: PR13
ref_type: Process
ref_name: "Monitor and Control Schedule"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.3.2.3"
companion_ref_shortcode: PG-APG-7.2
related_skills:
  - SKL-05-04
related_artifacts:
  - A15
  - A17
file_path: "reference/processes/PR13-monitor-and-control-schedule.md"
---
# PR13 — Monitor and Control Schedule

## Classification
- **Performance Domain:** Schedule
- **Process Group:** Monitoring and Controlling
- **PMBOK 8 Reference:** Section 2.3.2.3
- **Process Groups Practice Guide Reference:** Section 7.2 (implied)

---

## Purpose
Monitor and Control Schedule is the process of monitoring the status of the project to update the project schedule and managing changes to the agreed-upon schedule. The key benefit is maintaining a realistic schedule throughout the duration of the project.

---

## Inputs
- Project management plan (schedule management plan, scope baseline, performance measurement baseline, product backlog)
- Project documents: lessons learned register, project calendars, project schedule, resource calendars, risk register, schedule data
- Work performance data
- Enterprise environmental factors
- Organizational process assets

---

## Tools & Techniques
- Data analysis: earned value analysis, burnup/burndown chart, performance reviews, trend analysis, variance analysis, what-if scenario analysis
- Critical path method
- Critical chain method
- Project management information system
- Resource optimization
- Leads and lags
- Schedule compression
- Branch and bound
- Velocity, daily coordination meetings, sprint reviews, backlog refinement (adaptive)

---

## Outputs
- Work performance information
- Schedule forecasts
- Change requests
- Project management plan updates (schedule management plan, schedule baseline, cost baseline, performance measurement baseline)
- Project documents updates

---

## Key Concepts
- Determines current schedule status, influences factors that create changes, manages actual changes as they occur.
- Reconsidering schedule reserves is part of this process.
- In adaptive approaches: tracks velocity, manages backlog reprioritization, conducts retrospectives.
- Changes to schedule baseline in predictive approach require integrated change control.

---

## Source Traceability
- PMBOK 8: Section 2.3.2.3
- Process Groups Practice Guide: Section 7 (Monitor and Control Schedule)

---

## Cross-References

| Related Item | Type | Relationship |
|---|---|---|
| A15 | Artifact | Primary artifact produced or updated by this process |
| A17 | Artifact | Primary artifact produced or updated by this process |
| SKL-05-04 | Skill | Skill that executes this process |

## Practitioner Notes

Practitioners executing this process should seek answers to the following questions:
1. Is variance analysis performed against the approved schedule baseline?
2. Are corrective and preventive actions documented and traceable to root causes?
3. Is the Schedule Performance Index (SPI) calculated and reported?
4. Are forecast completion dates updated and communicated to stakeholders?
5. Are approved schedule changes reflected in an updated baseline?

## Change Log

| Version | Date | Description | Author |
|---|---|---|---|
| 1.0.1 | 2026-06-03 | Added Cross-References, Practitioner Notes, and Change Log sections (F-12 Batch 4) | PMO Director |
