Decision Lab · Dependency, float and critical-path change
A delay can change which path controls
Recalculate both complete paths. Do not add an activity delay directly to project duration.
By the end of this workshop
- Choose a method that respects the supplied conditions.
- Explain how a changed condition affects the decision.
- Identify a physical or procedural cross-check and an applicability limit.
- Record the assumption you would verify next time.
Start with the complete model
Givens and assumptions
- Original network: A precedes B and C; D starts only when both B and C finish. No resource constraints or calendars alter the network.
- Durations in working days: A = 3, B = 7, C = 6, D = 4. All activities use finish-to-start dependencies.
Study calculator, scratch notepad and whiteboard
Sketch a control volume or air path with a mouse, pen or touch. Ink stays in this page session and clears on reload. Use the response and reflection fields as a keyboard alternative. Sign in before starting and save a reflection to retain your reasoning.
1 · Choose the method
For A = 3, B = 7, C = 6 and D = 4 with D waiting for both branches, what completion time governs?
2 · Change the condition
Predict before you inspect the calculation.
C's duration becomes nine working days; all dependencies and other durations remain.
- A precedes parallel B and C; D waits for both. Durations A = 3, B = 7, C = 9, D = 4 working days; no resource/calendar changes.
Check the first decision to open the changed-condition response.
Reference navigation drill
Search concept: critical path, total float
Write the two complete paths before comparing them. Explain why the shortest path does not govern whole-project completion.
Where this model stops
Original simplified dependency network; real schedules also need calendars, resource limits and actual progress.
Found an unclear condition or calculation? Include workshop critical-path-switch and the step in your comment.
Share private feedback →