PERT swimlanes grouped by team
The same computed activity-on-node schedule, re-grouped into horizontal swimlanes by responsible team (Customer Account, Shopping Site, Shopping Cart, Testing) — the way Visual Paradigm and PMO templates present a project network.
For the delivery lead
A flat network answers "what's the critical path?"; a swimlane network also answers "who owns what?". Add lane: "…" to any task and the diagram re-groups into horizontal bands — by team, phase, or owner — without changing a single number in the schedule.
Same engine, different presentation. This is still pure activity-on-node: the forward/backward pass runs exactly as it would without lanes, so the critical path T2 → T3 → T4 → T7 → T8 and every slack value are identical to the ungrouped layout. Lanes are a view, not a computation — they activate automatically the moment any task declares one.
Reading the bands. Lanes appear in first-declared order, each as a banded row with a label gutter on the left. A task sits in the column for its dependency depth but the row for its team, so you can trace both the time order (left to right) and the ownership (top to bottom) at a glance. Dependencies that cross teams — T1 (Customer Account) and T4 (Shopping Site) and T6 (Shopping Cart) all feeding T7 (Testing) — render as orthogonal connectors hopping between bands, making hand-off points obvious.
Where this helps. This is the format PMO templates and tools like Visual Paradigm use for status reviews, because a stakeholder can find their team's row instantly and see what it's waiting on and what's waiting on it.