---
ref_id: PR12
ref_type: Process
ref_name: "Develop Schedule"
version: "1.0.0"
status: Active
pmbok8_source: "PMBOK8 Guide §2.3.2.2"
companion_ref_shortcode: PG-APG-5.10
related_skills:
  - SKL-03-06
related_artifacts:
  - A15
file_path: "reference/processes/PR12-develop-schedule.md"
---
# PR12 — Develop Schedule

## Classification
- **Performance Domain:** Schedule
- **Process Group:** Planning
- **PMBOK 8 Reference:** Section 2.3.2.2
- **Process Groups Practice Guide Reference:** Section 5.10

---

## Purpose
Develop Schedule is the process of analyzing activity sequences, durations, resource requirements, and schedule constraints to create a schedule model for project execution and monitoring and controlling. The key benefit is that it generates a schedule model with planned dates for completing project activities.

---

## Inputs
- Project management plan (schedule management plan, scope baseline)
- Project documents: activity attributes, activity list, assumption log, basis of estimates, duration estimates, lessons learned register, milestone list, project schedule network diagrams, project team assignments, resource calendars, resource requirements, risk register
- Agreements
- Enterprise environmental factors
- Organizational process assets

---

## Tools & Techniques
- Schedule network analysis
- Critical path method (CPM)
- Critical chain method
- Resource optimization (resource leveling)
- Data analysis (what-if scenario analysis, simulation)
- Leads and lags
- Schedule compression (fast tracking, crashing)
- Project management information system
- Agile release planning

---

## Outputs
- Schedule baseline
- Project schedule
- Schedule data
- Project calendars
- Change requests
- Project management plan updates (schedule management plan, cost baseline)
- Project documents updates

---

## Key Concepts
- Four steps: (1) Define activities, (2) Determine sequence, (3) Estimate effort and duration, (4) Adjust.
- Developing an acceptable project schedule is an iterative process.
- Schedule baseline is the approved version of the schedule model; changes require formal change control in predictive approaches.
- Schedule flexibility and reserves (float, contingency) are built in for known risks.
- Critical path determines the minimum project duration.

---

## Adaptive Considerations
- Agile release planning maps user stories to iterations and releases.
- Velocity and burndown/burnup charts monitor adaptive schedule progress.

---

## Source Traceability
- PMBOK 8: Section 2.3.2.2
- Process Groups Practice Guide: Section 5.10

---

## Cross-References

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

## Practitioner Notes

Practitioners executing this process should seek answers to the following questions:
1. Is the critical path identified and documented with float analysis?
2. Have schedule compression techniques (crashing, fast-tracking) been evaluated?
3. Are resource constraints and calendars fully reflected in the schedule model?
4. Is the schedule baseline formally approved before execution begins?
5. Are schedule reserves (buffer) documented and linked to specific risks?

## 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 |
