Skip to content
Gantt & critical path templates

Relative Plan — Day Numbers, Because No Date Was Stated

A plan with no start date is still a plan: five days, then ten, then three. The engine schedules it, computes the critical path and the float, and draws the axis in DAY NUMBERS — because inventing a Monday would put a fabricated Tuesday under every bar and a fabricated weekend in the middle of one. There is deliberately no `calendar` line either: with no date there is no way to know which day is a Saturday, so declaring a working week here would declare something the engine cannot apply — and it says so if you do. Add `start 2026-03-02` and every bar becomes a date, on the week you then declare, without another edit.

Template previewGantt & critical path
Sprint zero — Gantt chart with critical path7 tasks; spanning 23 working days with no stated start date; 6 on the critical path; every check ran and found nothing.Sprint zeroday 1 → day 23 · no start date stated, so this axis is in day numberscritical path: repo → env → model → api → ui → demoshorten first: model (up to 6d) · env (up to 5d) · api (up to 5d)day 1day 3day 5day 7day 9day 11day 13day 15day 17day 19day 21day 23working days from the start — this plan states no calendar dateSet-upFirst slice▲ Repository and CI3d · shorten → 3d▲ Environments5d · shorten → 5dAuth spike4d · float 7d▲ Domain model6d · shorten → 6d▲ Thin API5d · shorten → 5d▲ Thin UI4d · shorten → 4d▲ Demoday 24critical — zero floatnear-criticalhas floattotal floatmilestonenon-working dayEvery check ran, and none of them found anything.·day 1 to day 23 — 23 working days, counted on a continuous week because this plan states no start date·one critical path, through 6 tasks — shortening any one of them shortens the project, up to the point another path becomes binding·to finish sooner, shorten `model` by up to 6 working days (the whole task); `env` by up to 5 working days (the whole task); `api` by up to 5 working days (the whole task). Anything beyond those figuresmoves nothing — the gain from taking δ days off a task is min(δ, the figure above), and it is zero for every critical task not listed here.

Make it your own.

title "Sprint zero"

section "Set-up"
  task repo  "Repository and CI" 3d
  task env   "Environments" 5d after repo
  task auth  "Auth spike" 4d after repo

section "First slice"
  task model "Domain model" 6d after env
  task api   "Thin API" 5d after model, auth
  task ui    "Thin UI" 4d after api
  milestone demo "Demo" after ui