Make a workable team delivery plan
Separate uncertainty, dependency timings and people availability before committing to a deadline.
Tools do not automatically transfer your results or save inputs. The linked case presets are fixed demonstration data.
Before you begin
Small project teams coordinating a short delivery
- An agreed task list
- Predecessor relationships
- Available hours for the same planning period
Describe uncertainty first
The three estimates give about 4.33 days expected duration and a one-day standard deviation for one uncertain task. This is a separate estimation exercise, not a probability of finishing the whole network.
Try the example in PERT three-point estimate ↗Inspect the dependency network
Brief → Build → Release takes seven elapsed project days. Review has one day of slack. The network uses supplied working durations and has no holiday calendar or resource leveling.
Try the example in Project critical path ↗Check people capacity separately
The heuristic assigns 18 hours to Ada and six to Sam. Neither exceeds the supplied period capacity. This separate workload check does not automatically prove the seven-day dependency schedule is feasible.
Try the example in Team workload allocation ↗Make the handoff explicit
Review the assumptions before adapting these figures. A calculated result is not an order, invitation, accepted quotation or guaranteed deadline. Save your own copy before leaving; no work is stored automatically.
Read the complete worked case ↗
Read the related explanations
PRACTICAL GUIDERead critical-path slack before checking team capacity
Work through a branching task network and see why a dependency schedule is not a staffing plan.
Read the guide
PRACTICAL GUIDEUse a decision matrix to expose assumptions, not hide them
Choose consistent score directions, test weights and distinguish close rankings from strong conclusions.
Read the guide