Project management practice
Project schedule example: show the dependency, not just the date
Build a small dependency-led schedule, calculate float, and explain what a delay changes before revising a delivery commitment.
Start with a finish condition
A useful schedule connects accepted deliverables, the work that produces them, and the decisions that release the next activity. A list of due dates hides the causal chain. Write what “done” means for each task before choosing its duration, and name the person who can accept the result.
Use one calendar and one time convention. The fictional office-access rollout below uses elapsed working days starting at day 0. It has no resource conflicts, holidays or partial overlaps; those would need explicit treatment in a real plan.
Worked example: two paths into the same handover
| Activity | Duration | Predecessor | Earliest start → finish |
|---|---|---|---|
| A · Confirm access requirements | 2 days | None | 0 → 2 |
| B · Configure devices | 5 days | A | 2 → 7 |
| C · Prepare staff briefing | 3 days | A | 2 → 5 |
| D · Test and accept | 2 days | B and C | 7 → 9 |
Explain the path that drives completion
A–B–D takes nine working days; A–C–D takes seven. In this simplified network, C can slip by two days before it delays D. B has no float. Adding three days to B moves forecast completion to day 12. Adding one day to C leaves completion at day 9.
A committed finish on day 11 creates two days of buffer beyond the original forecast. If B takes three extra days, that buffer is consumed and the commitment is missed by one day. The baseline remains day 11 until an authorised change is recorded; changing the spreadsheet date is not approval.
Copyable schedule review
Deliverable and acceptance evidence: Activity / duration / calendar: Predecessors and relationship: Owner and shared resource constraints: Baseline finish / current forecast: Float or buffer and how calculated: Assumptions awaiting confirmation: Decision needed / decision owner / latest useful date:
Before you publish it
Ask owners whether the durations include review, rework and handover. Check that a shared specialist is not scheduled on two simultaneous tasks. Record supplier confirmations as evidence rather than assuming an email request is a commitment.
If a date moves, update the forecast, the affected risk or issue, the sponsor message and any change request together. A beautiful chart is not a complete delivery explanation. Use the delivery-check tool to rehearse one simplified delay; it does not calculate a network critical path.
Method background
These sources provide general background. The worked examples and worksheets are original Response Shift teaching material; the organisations do not endorse this product.
