Sprints, estimates and workload

Estimates

Open an item and type into Estimate. The value is stored in whole minutes and shown as a badge on rows and cards. These spellings are all accepted:

Clear the field to remove the estimate. Estimates are optional everywhere: sprints and workload count items until something has an estimate.

Sprints

Create one

1. Open Sprints from the sidebar and choose New sprint.
2. Give it a name, an optional goal, and start and end dates.
3. Choose the scope: one board, so only that board's items can join it, or workspace-wide, so it appears in every board's sprint picker.

Workspace owners, admins and members can create, start and close sprints. Sprints are on every plan.

Put items in a sprint

Open an item and pick the sprint in the drawer's Sprint field. The list shows the board's own sprints and the workspace-wide ones; closed sprints are not offered. On the board, the filter bar has a Sprintfilter so any view can show one sprint's items.

Planned, Active, Closed

• Planned: created but not started. Fill it while the current sprint runs.
• Active: one at a time per scope, so one per board plus one workspace-wide. Starting a sprint while another is active asks you to close the running one first.
• Closed: finished. Its items keep their sprint for the record.

Progress and burndown

Each sprint shows shipped items over total items and, when any item has an estimate, estimated hours done over hours total. The active sprint draws a burndown: open items per day (solid line) against a straight line from every item open on day one to zero on the end date (dashed). The chart counts items, not hours.

Close a sprint

Choose Close sprint. If items are still open you pick where they go: the next planned sprint in the same scope, another sprint, or the backlog (no sprint). Nothing is deleted or marked done on your behalf.

Workload

Open Workload from the sidebar. The grid has one row per member and one column per week for 8 weeks, plus columns for Overdue, Later and No date so nothing hides outside the window. Use the arrows to move the window earlier or later.

• Count items shows how many of the person's items are due that week. Sum hours adds up their estimates instead.
• Cells are shaded against the person's weekly capacity, so an overloaded week stands out.
• Capacity is the sum of the hours on the days each person marks as working in their profile. When nothing is set, 40 hours a week is assumed.
• An item with two assignees counts for both of them.
• Hide done removes finished items; the board chips limit the grid to chosen boards.
• Click a cell to list its items. Change an item's due date there and it moves to the matching week.

Private boards a person cannot open are left out of the sprints and workload they see, the same rule as everywhere else in the workspace.

Related

• Boards and columns for the Timeline and Dependency columns behind the Gantt.
• Goals for outcomes that span more than one sprint.
• Dashboards for progress and timeline widgets over the same items.