Two-axis model for classifying projects by What / Requirements (clear ↔ unclear) and How / Approach (known ↔ untested). Determines the appropriate PM method.
- Prerequisite: dependencies between work packages known
- Foundation for schedule and resource planning
- Key questions: Which WPs must finish first? Which run in parallel?
- WBS shows What — Sequence Plan shows In what order
- Created for each element of the sequence plan
- The more complex (→ Stacey), the harder the estimation
- No exact method — best done by experts
- Result feeds directly into the project schedule
- Typical unit: weeks per work package
- Shows each activity with a concrete start and end date
- Does not include a view of available resources
- Constraints to consider: calendar, holidays, steering committees
- Formats: Network diagram or Gantt chart
- Protects the schedule against unforeseen delays
- Activities without buffer lie on the critical path
- Deliberately planning buffer = good project management
The longest sequence of activities that determines the project end. WPs on it have TF = 0 (no total float).
- TF = 0 — any delay endangers the project end
- Requires highest management attention
- Assign resources with priority
- TF > 0 — delay up to float length is tolerable
- Provides flexibility in resource allocation
- Can be treated as lower priority
Critical Path (TF=0) Non-critical (TF>0) ◆ Milestone
Critical Path Non-critical Float ◆ Milestone
- Clearly and unambiguously defined
- Achievement must be verifiable beyond doubt (yes/no)
- Always assigned to a work package
- Basis for progress measurement & controlling
- Analysis completed
- Concept approved by client
- Pilot successfully signed off
- Project closure / go-live
IT Security project: training, awareness & monitoring. Deliverables per group:
Forward pass: ES = 0 for the first WP; ES of successor = max(EF of all predecessors). Backward pass: LF of last WP = EF of project end; LF of predecessor = min(LS of all successors).
TF = 0 lie on the critical path. Any delay on this path delays the entire project.EF = ES + D. ES of successor = max(EF of all predecessors).Backward pass (latest dates): Start at the last WP: LF = EF of project end.
LS = LF − D. LF of predecessor = min(LS of all successors).Total Float:
TF = LS − ES.
- Be clearly and unambiguously defined
- Be verifiable beyond doubt (yes/no — not "80% reached")
- Be assigned to a specific work package
- Serve as a basis for progress measurement and controlling
It does not contain a resource view — i.e. who does the task or with what budget. That is the job of resource planning.
Gantt chart: Shows the time axis and parallelism of WPs more intuitively, but dependencies and float values are less directly readable.
Both complement each other — in practice both are often used together.