Syncronaus build

Minimum product first. Position as of — · last updated — · the Archive phase is an estimate of 30 lane-days until its plan exists.

—
——

Minimum product

— of — lane-days done, weighted by status. The arrow is the change over the 7 days before.

Phases

percent complete
Projected landing
—
at the last — days' pace · whole build: —
Remaining
—lane-days
of — planned
Pace
—a day
lane-days, last — days · whole build —

Spread

calendar days consumed against planned lane-days, per phase

A phase whose consumed days (filled) reach past its plan (dashed) is where time has gone. The bars say the same in a form that is easier to compare.

What is moving

—

Burn-up to the minimum product

lane-days done against the planned scope, with the pace of the last 14 days continued to where it meets the scope

Timeline

every phase and lane: what has happened in colour, what is modelled in grey · click a phase to open or close its lanes
Being builtIn final checksLandedPlanned, when the phase plan sets datesModelled: remaining lanes in phase order, — at a time, — calendar days per planned day as landed lanes have taken

—

Percent complete counts each lane by its planned days times how far along it is (not started 0, being planned 0.1, being built 0.4, in final checks 0.8, landed 1). A lane in final checks for more than three days, or built for longer than one and a half times its plan, is flagged. Phases marked as coming after the minimum product are not needed for the first release.

Standalone copy generated 2026-11-03T17:21:19+1100 from the build state file; the figures refresh daily at 08:00.