# Trackwell Sprint Burndown

> Sprint burndown and burnup from a Trackwell project or a table of sprint items. Draws the burndown (remaining work per day against the ideal line) and burnup (completed work and scope) of a sprint. Reads a Trackwell project and rebuilds the sprint from the issue history, or takes a simple table of items with points and the moments they were added, removed and finished.

Part of usefulweb.app (https://usefulweb.app/). Part of [Trackwell](https://trackwell.usefulweb.app/) (ownerApp: trackwell). Results are deterministic calculations from the inputs and the listed assumptions; the API returns exactly what the web page shows.

## Use it
- Human interface: https://trackwellburndown.usefulweb.app/ (interactive tool at https://trackwellburndown.usefulweb.app/tool)
- JSON API: POST https://trackwellburndown.usefulweb.app/api/v1/calculate with a JSON object of inputs (schema: https://trackwellburndown.usefulweb.app/api/v1/tool)
- OpenAPI: https://trackwellburndown.usefulweb.app/openapi.json
- MCP (Streamable HTTP): https://trackwellburndown.usefulweb.app/mcp - tool `trackwell_burndown`

## Inputs
- project (textarea): Trackwell project (JSON, optional) - A .trackwell.json project with sprints. Leave empty to use the items table below.
- sprint (text): Sprint name - Empty = the active sprint (or the last completed one).
- start (date): Sprint start (items table only)
- end (date): Sprint end (items table only)
- items (table): Sprint items - Dates as YYYY-MM-DD (counted at the end of that day) or YYYY-MM-DDTHH:MM.
- unit (select): Measure
- asOf (date): Today is - Days after this date are left empty. Empty = today.

## Method
- Each day is counted at its end (23:59:59 UTC). Scope = points (or issues) in the sprint at that moment; completed = scope items that are done; remaining = scope − completed.
- Committed = scope at the start of the first day (items added on the start day count as committed). The ideal line falls linearly from the committed value to zero on the last day.
- From a Trackwell project the items are rebuilt from the issue history: when an issue entered or left the sprint, when it last moved into a “done” status, and its story points. Sub-tasks are left out (their parents carry the points). A completed sprint is evaluated up to the moment it was completed, so carried-over issues stay in its open list.
- Added = items that joined after the first day (scope creep); removed = items taken out during the sprint.