Project schedule management is the most critical constraint because time is the least flexible resource — it passes regardless of what happens on a project, unlike cost or scope which can often be renegotiated.
- Schedule issues peak during the middle and end phases — precisely when pressure is highest.
- Cultural differences also cause conflicts: some cultures treat deadlines as strict while others treat them loosely.
- Technical errors, poor communication, and weak scope management further amplify schedule overruns.
| Feature | AOA / ADM | PDM / AON |
|---|---|---|
| Activity shown as | Arrow | Box (node) |
| Nodes represent | Start/end events | Activities |
| Dependency types | Finish-to-Start only | All 4 types (FS, SS, FF, SF) |
| Dummy activities | Needed for shared predecessors | Not required |
| PM Software | Rarely used | Industry standard (MS Project) |
Forward Pass rules:
- ES of first activity = 0. EF = ES + Duration
- When multiple paths converge, take the largest (latest) EF
Backward Pass rules:
- LS of last node = its ES. LF = LS of successor
- LS = LF − Duration. When multiple paths diverge, take the smallest LS
Activities B, E, H, and J all have Total Float = 0. Any delay on these activities will directly delay the project finish date of 16 days.
- Free Float ≤ Total Float always.
- Critical path activities always have Total Float = 0.
- If two activities converge to one successor, only one can have free float.
- In Project X: Task F has the most slack (Free = 7d, Total = 7d) — it's the most flexible.
Without PERT a PM would use 10 days (most likely). PERT gives 12 days — accounting for the risk of the pessimistic scenario. The extra 2 days reflects the right-skewed uncertainty typical in IT projects.
Three-point estimates are also required for Monte Carlo simulations, which model thousands of schedule scenarios to quantify overall project risk.
Key terms:
- Crash Duration — shortest possible time an activity can be completed.
- Additional Cost/Day — extra cost per day of compression for a task.
- Project Overhead/Day — daily overhead saved by reducing the total project duration.
| Symbol | Meaning |
|---|---|
| ◆ Black diamond | Milestone (zero-duration significant event) |
| Thick black bar | Summary task (WBS parent) |
| Lighter bar | Individual task duration |
| Arrow between bars | Dependency between tasks |
| ◇ Open diamond | Slipped milestone (completed later than planned) |
| Top/Bottom bars | Tracking: planned (top) vs actual (bottom) |
Milestones must satisfy SMART criteria: Specific, Measurable, Assignable, Realistic, Time-framed.
| Advantage | Disadvantage |
|---|---|
| Easy to read and communicate | Does not naturally show dependencies |
| Standard industry format | WBS logic can be obscured at scale |
| Tracking variant shows planned vs actual | Dependency arrows only appear if tasks are linked in software |
- Project Buffer (PB) — time added before the final project due date. Protects the delivery date from accumulated delays on the critical chain.
- Feeding Buffer (FB) — time added before a critical chain task if preceded by non-critical tasks. Prevents off-path delays from propagating into the critical chain.
- Multitasking — critical chain minimises simultaneous task assignments because humans perform poorly when switching contexts frequently.
- Murphy's Law: "If something can go wrong, it will." People pad individual estimates. Critical chain removes task-level padding and consolidates protection into shared buffers.
- Parkinson's Law: "Work expands to fill the time allowed." Without individual buffers, teams focus on actual work duration rather than filling allocated time.
| # | Process | Key Output |
|---|---|---|
| 1 | Plan Schedule Management | Schedule management plan |
| 2 | Define Activities | Activity list, attributes, milestones |
| 3 | Sequence Activities | Network diagram with dependencies |
| 4 | Estimate Activity Resources | Resource requirements per activity |
| 5 | Estimate Activity Durations | Duration estimates (PERT, 3-point) |
| 6 | Develop the Schedule | Project schedule, schedule baseline, schedule data, project calendars |
| 7 | Control the Schedule | Progress reports, variance analysis, earned value |
The primary outputs of Process 6 (Develop Schedule) are the project schedule, a schedule baseline, schedule data, project calendars, and project management plan/document updates. Key tools include Gantt charts, CPM, PERT, and Critical Chain Scheduling.