Agile & SprintsModule 244 apps
Plan work in iterations, and see what actually got done Coming by Holi
Thirteen lines of the specification that amount to one board, one boundary and one chart. It sits beside Projects & Collaboration rather than inside it because a task list and a sprint are different disciplines: a task is either done or not, while a sprint asks how much a team reliably finishes in a fixed period and holds that answer against the last one. A business running a factory may never want any of this, which is precisely why it is a module that can be left switched off instead of something bolted onto the task list everybody uses.
Reads fromProjects & CollaborationHR & Payroll
Writes toProjects & Collaboration
Part of Work & Collaboration
4 apps in Agile & Sprints
Product Backlog & Stories
The queue of work that has not been started, written as something a person wants rather than a task somebody was handed, grouped under the larger outcome it belongs to and sized relative to the others. Sizing is deliberately relative and not in hours, because the one thing teams estimate consistently is whether a piece is bigger than another piece.
Sprints & Boards
A fixed period with a set of work committed to it, and a board showing where each piece has got to. The boundary is the point: work added midway is visible as having been added midway, so the difference between what was planned and what was delivered stays legible instead of being quietly absorbed. Planning at the start and a review at the end are part of the same record, not meetings held somewhere else.
Velocity & Burndown
How much this team actually finishes per period, and how the current one is tracking against what remains. Both are read from the board rather than typed by anybody, which matters because a progress figure a person types is a figure a person can round.
Release Planning
Which finished work goes out together and when, drawn from what the sprints have actually completed rather than from what was hoped for at the start. A release date derived from delivered work is the only kind that survives contact with the second sprint.