Time-scaled migration plan (network-Gantt)
A data-centre migration in the time-scaled layout — x-position proportional to Early Start, width proportional to duration, with a unit time axis. Exercises start-to-start and finish-to-finish dependencies, lag/lead, a milestone, and lane packing.
For the program manager
layout: timescaled is the bridge between the network view and a Gantt chart. Each activity's x-position is proportional to its Early Start and its width is proportional to its duration, with a unit time axis along the bottom — so distance reads as time.
Full PDM dependencies. This network uses every relationship type beyond the default finish-to-start. B after: A SS+1 is start-to-start with a 1-day lag (stakeholder review begins a day into the inventory). E after: C+2 is FS with a 2-day lag (procurement waits two days after vendor selection finishes). G after: ... F FF is finish-to-finish (the pilot environment must be ready when the code refactor finishes, not after it). Each non-FS edge is labelled on the connector (SS+1d, FS+2d, FF).
Milestones and lane packing. Cutover is declared with the milestone flag — a zero-duration checkpoint drawn as a diamond at its scheduled date. To avoid overlaps, activities are greedily packed into horizontal lanes by start time, and task names sit above their bars (Gantt convention) so long labels never overflow a short bar.
Still computed, still critical-aware. Even in the time-scaled view the critical path is highlighted in red and slack is shown on each bar. Procurement (E) carries 6 days of slack and renders in blue, visibly off the critical chain A → C → D → F → G → H → I → J.