Role capacity & bottlenecks
Set max heads per role (blank = unlimited). A role is a bottleneck when max heads is below the heads needed to run every selected task in parallel. Overrun means the role cannot finish within the quarter at the given head count.
Burndown — remaining effort (days) per working day
Fluid capacity model: the line shows total remaining effort across all roles; each role burns min(max heads, parallel demand) person-days per working day. Per-role finish days are in the capacity table above. Dashed vertical line = quarter end.
Tasks (41)
Tick to include a task in the scenario. Effort cells are Demand in working days per role (source FTE × quarter working days); all editable, coral border when edited. Click any column header to sort (click again to reverse). The summary row under the headers sums the Demand of included tasks per role — the same totals as Demand (days) above. Priorities are editable per task; the priority buttons toggle every task of that priority on or off (highlighted = all tasks of that priority selected). Use Save changes to persist your edits in this browser.
Assumptions
Rocket-themed 2026-Q3 dataset: task numbers, estimates, priorities, sizes, and statuses are unchanged; only titles and role names differ. Demand (days) for each task is driven by the quarter length: source FTE × quarter working days (default 65). Changing the quarter working days rescales every unedited demand cell; changing 1 FTE = days/quarter does not change demand — it only rescales "Heads needed in parallel" (= demand ÷ FTE days per quarter). Effort is freely divisible across heads within a role (optimistic). "Heads needed in parallel" is the staffing required if every selected task ran simultaneously. With unlimited heads every role finishes within one FTE period (the FTE days/quarter value), since each allocation progresses at its own FTE rate. Edits can be persisted in this browser with Save changes and restored automatically on reload. "Partial" allocations on #113 are counted in full. The #44 Software and #45/#46 spike allocations are conditional in the source. Closed and deferred tasks default to excluded but can be toggled in. Burndown ignores dependencies (e.g. #112 requires #126) and sequencing between tasks. 19 tasks have no priority. Priority edits made here are scenario-only.