Building
Where the team turns the planning record into working software: the sprints it plans and commits to, the board it works them on, with the time tracking, the definitions of ready and done and the Git links joining as they land.
The build phase reads the planning record the business analyst wrote and turns it into shipped work. The backlog already holds the stories, tasks, bugs, spikes and improvements; building is how the team takes them on in order: a sprint is planned with its dates and a goal, takes its scope from the backlog, starts when the team commits to it, and closes with the points it finished kept as its velocity and the unfinished work carried on. The board shows that scope as columns, one per status, and a card dragged between them is the same move the backlog makes. Everything the team does in a sprint stays on the items themselves, so the record a tester, a release manager or a client reads later is the same record the developer worked from.
| Piece | What it is |
|---|---|
| Sprint | A dated run of work numbered within the project, with a goal, a capacity in points and hours, a scope of work items, the team's commitment that starts it, the points it committed to and finished, its velocity and a retrospective. One sprint of a project runs at a time. |
| Board | The running sprint's items, or any scope of the backlog, in a column per status: dragged along the lifecycle and into their place in the order, under the limits each column keeps, laid out by epic, person or kind. |
The definitions of ready and done, time tracking, the Git links and the CI reports join this section as each module lands, and each gets its own page here.
Where sprints meet the rest of the record
A work item carries the sprint it is planned into beside its epic, so the backlog filters by sprint, the sprint's flyout lists its scope, the board follows the running sprint, and an agent plans an item through the item itself. The commitment that starts a sprint is an approval like any other, decided by the people the project's policy names.
Board
The sprint's work in columns: drag a card along its lifecycle and into its place, keep each column under its limit, lay the cards out by epic, person or kind.
Sprints
Plan a sprint, pull its scope from the backlog, put it to the team for its commitment, run it, close it with its velocity and carry the unfinished work on.
Backlog
The items a sprint takes on, with their estimates, people and acceptance criteria.
Approvals
The sprint commitment beside the other gates: who decides, the inbox and the verdicts.
How is this guide?
Last updated on
Change Requests
Raise a change request against a frozen baseline, name the records it touches, write or ask Heimdall for the impact on scope, schedule, effort, cost and risk, convene the council, submit it to the approvers whose agreement unlocks the records named, and see the change through to verified.
Board
The Board page of a project: the running sprint's work in a column per status, dragged along its lifecycle and into its place in the order, with the limits each column keeps, swimlanes by epic, person or kind, and the quick filters.