driftless
Search As of 2026-07-01

Schedule network — Season 4 Rollout

As of 2026-07-01 · Schedule · Project hub

Tasks in network9
Critical paths2
Project buffer0.0d

Network

Baseline version 1. Each box is a task; a solid, thicker edge marks the critical path.

1 (35d) 2 (14d) 3 (14d) 4 (35d) 5 (35d) 6 (14d) 7 (11d) 8 (12d) 9 (6d)
Every task in the network and its dependencies
TaskDurationOn critical pathDepends on
Shoot schedule35dYes —
Music clearance35dNo —
Dailies review14dYes Shoot schedule
Assembly edit14dYes Dailies review
Rough cut35dYes Assembly edit, Shoot schedule
Colour grade14dYes Rough cut
Sound mix11dNo Rough cut
Broadcast QC12dYes Colour grade, Music clearance, Sound mix
Delivery to network6dYes Broadcast QC

Critical paths and float

Earliest/latest start and finish, and float, per task
TaskESEFLSLFTotal floatFree floatCritical
Shoot schedule035 0350d 0dYes
Music clearance035 498449d 49dNo
Dailies review721 7210d 0dYes
Assembly edit2135 21350d 0dYes
Rough cut3570 35700d 0dYes
Colour grade7084 70840d 0dYes
Sound mix7081 73843d 3dNo
Broadcast QC8496 84960d 0dYes
Delivery to network96102 961020d 0dYes

Preview a scenario

A preview is read-only — nothing here changes the stored plan. Try a crash (shorten one critical task, at its cost per day) or a fast-track (overlap one critical finish-to-start pair) and see how the network's dates and float would move.

Crash candidates on the critical path, cheapest first: Dailies review ($0.0/day), Assembly edit ($0.0/day), Colour grade ($0.0/day), Broadcast QC ($0.0/day), Delivery to network ($0.0/day), Shoot schedule ($171.43/day), Rough cut ($257.14/day).

Fast-track candidates on the critical path: Shoot schedule → Rough cut, Dailies review → Assembly edit, Assembly edit → Rough cut, Rough cut → Colour grade, Colour grade → Broadcast QC, Broadcast QC → Delivery to network.

Resource levelling preview (every non-critical task shifted to its latest start): peak demand 3.0 → 3.0.

Critical chain (Driftless extension)

Not a PMBOK-6 clause — no numbered process names this technique (tt.EXTENSIONS). The project buffer is sized at half the safety recorded on the critical chain's own three-point estimates; a feeding buffer, also half its task's own safety, sits wherever a non-critical task merges directly into the chain. A task with no three-point estimate on record contributes zero safety here — never an invented figure.

Critical-chain safety: 0.0d · project buffer: 0.0d.

One feeding buffer per non-critical task merging into the critical chain
TaskFeeds intoBuffer
Music clearanceBroadcast QC0.0d
Sound mixBroadcast QC0.0d

Propose this as a baseline change

This writes nothing to the plan itself: it files a draft baseline carrying the preview above and a change request describing it. Approving the change and promoting the draft to the live plan is a separate, existing step (PATCH /baselines/<id>, then PATCH /change-requests/<id>) — never done here.

Where this comes from

PMBOK-6 process 6.5 (Develop Schedule) · as of 2026-07-01 · source PMBOK Guide, 6th edition. Critical chain method is a Driftless extension, cited to none of the above.

← Back to Season 4 Rollout hub