Schedule and resource management
Schedule and resource management
This domain tests network logic, critical path, float and resource optimisation.
Core rules
- Build a precedence network with dependencies (FS, SS, FF, SF) and lags.
- The critical path is the longest path; its total float is zero, or negative if constrained. Total float is the time an activity can slip without delaying project finish; free float is slip without delaying any successor.
- Use resource levelling when demand exceeds availability; it may extend the schedule. Smoothing shifts work within float to balance peaks.
- Schedule compression: crashing adds resources or cost; fast tracking overlaps activities and adds risk.
- Baseline the schedule and track progress against it.
Worked example
Activities: A takes 3 days; B takes 4 days after A; C takes 2 days after A; D takes 5 days after B and C. Paths: A-B-D = 3+4+5 = 12 days; A-C-D = 3+2+5 = 10 days. The critical path is A-B-D with duration 12 days. C has total float of 2 days and free float of 2 days because D cannot start until B finishes at day 7. Reasoning: float comes from forward and backward pass, not by eye.
Traps
- Treating the longest activity as critical.
- Confusing total float with free float.
- Crashing without checking cost-benefit or new risks.
- Levelling resources and forgetting to re-baseline.
- Ignoring calendars, holidays and part-time availability.