Virtual Walk the Walls™
Reading the dependency legend
Five levels, from standalone work through to the highly entangled sections that are hardest to exit.
- Critical path. A blocking item where slippage delays the whole programme. Flagged from red status with dependencies, three or more dependencies carrying overdue tasks, or the latest due date in the project.
- No dependencies. Standalone work that can be executed independently. On a TSA service schedule these are the ones to exit first.
- 1 dependency. One upstream workstream to coordinate with. Track it and sequence accordingly.
- 2 dependencies. Multiple upstream items and higher coordination risk. Worth active IMO tracking.
- 3+ dependencies. Highly entangled across workstreams. These are the hardest to exit, and on a carve-out they are often where the seller has embedded pricing leverage.
Virtual Walk the Walls™
Can't find what you're looking for? Contact support