Prepare and manage Sprints

Use a Sprint to plan a period of project work, then follow it day to day with Team Pulse. You decide when it starts and completes. A Milestone groups work toward an outcome; a Plan keeps related tasks together. A task can belong to one of each at the same time.

• Sprints must be enabled in Project Settings. You can use them with Milestones switched off.
• Project members can view Sprints and prepare Planned Sprints.
• Team Leads and organization owners or admins with project access can start, complete, reopen, correct history, and edit Current or Complete Sprints. They also manage membership on the Sprint page. Members can make Scope changes through ordinary task editing.

Open Sprints from the project navigation. The Current Sprint appears first, followed by Planned and Complete Sprints. Select a card to see its schedule, objective, tasks, progress, and Team Pulse.

1. Select Create Sprint and enter its title and optional Markdown Objective.
2. In Schedule, choose the planned start and end. Dates and times use the current Organization time zone.
3. Select Create Sprint. It is saved as Planned; creating it does not start it.

Set the start first, then choose how to set the end:

1. Under Plan the start, choose Choose a date to enter the new Sprint's planned start. Add a time if you need one. To put it after an existing Sprint instead, choose After another Sprint, then pick the earlier Sprint in Sprint starts after. This fills in the new Sprint's start from the earlier Sprint's planned end.
2. Under Plan the end, choose the duration option, such as Use 21-day Sprint duration, to calculate the end from the new Sprint's planned start. The number shown comes from Sprint duration in Project Settings. Changing the start updates the calculated end.
3. To enter a different end, choose Choose a custom end, then enter its date and optional time. A custom end stays as you entered it when you change the start.

For example, a 21-day Sprint starting October 21 with no time runs through November 10, including both dates. If it starts October 21 at 09:00 instead, the calculated end is November 11 at 09:00. When following a Sprint that ends at end of day, the new start is the following day; when that Sprint has an end time, the new start is that same boundary.

Review Planned start and Planned end before saving. Calculated dates are read-only previews; change the choices above them to adjust the schedule. The earlier Sprint is unchanged, and neither Sprint starts automatically. Switching modes keeps your manual drafts.

Edit Sprint opens saved dates in manual/custom mode, so a title edit does not recalculate them. An unknown start shows Not set. Clear planned start removes it and keeps the end as a custom end. If no suitable reference Sprint is available, enter dates directly. Failed saves keep your draft; reload and review if someone changed the record.

Use the calendar or keyboard to choose a date, then Apply or Cancel. A start without a time means the start of that day; an end without a time means its end. The start must precede the end. Sprint duration counts local calendar days, so a daylight-saving change can make a day shorter or longer than 24 hours. If you enter a clock time skipped or repeated by that change, choose a different time. A Current or Complete Sprint's planned end must not precede its actual start.

Changing planning dates does not change when the Sprint actually started or completed, its tasks, or their outcomes.

Planned means prepared, Current means started, and Complete means completed. A project can have several Planned Sprints and only one Current Sprint. These labels are separate from task states such as Done and Closed.

On a Planned Sprint, select the green Start Sprint button, review Start date and time, then confirm. The time is shown in the current organization zone and cannot be edited in this dialog. Starting saves the Sprint's tasks and estimates as its opening plan. It does not change task states or planned dates. Cancel starts nothing.

If another Sprint is Current, Start Sprint is disabled. Hover or focus its explanation to identify the Sprint to complete first. Reload if the record, settings, or your access changed. A planned date arriving, queueing a task, or starting a task never starts its Sprint. Sprint deletion and CLI Sprint record/lifecycle commands are unavailable.

Managers can complete a Current Sprint and safely reopen an eligible Complete Sprint. You can also complete and start a prepared following Sprint in one confirmation.

The Horizon at the top of the page puts dates and progress together. Dates include the current organization time zone. A Current Sprint shows Day N, time until or past its planned end, and a diamond marking the current moment on the timeline. Day numbers count calendar dates in that zone. The Sprint continues past the planned end until someone completes it.

Tasks completed and Total Size completed compare completed work with the opening plan, including Corrections. The planned-end marker stays visible when a Sprint runs late or completes early. Values can exceed the plan. They describe what happened, rather than forecasting delivery or rating the team.

Only Done tasks contribute completed work. Total Size adds Coding-agent Mass and Person Weight using known estimates. Tasks marked Exclude from metrics do not contribute. A dash means a value is unavailable. Later Scope changes do not replace the opening plan used for this comparison.

A Complete Sprint stops at its completion time and shows its final values and closing day. A Planned Sprint shows Planned start, Planned end, Tasks, and Total size, with Not set for an unknown start. It previews scope rather than completed work.

Progress unavailable means the saved history cannot support that part of the chart; available task totals may still appear. A failed request offers Try again. Dates remain readable text, including for screen readers, and motion follows your reduced-motion preference.

The Task count and Total Size charts show how work changed over time. Completed means Done. Remaining includes unfinished and Closed tasks still in the Sprint. Their upper boundary shows total scope, including later Scope changes; the Horizon comparison above them keeps the opening plan.

Total Size stacks completed Coding-agent Mass and Person Weight, with a separate line for total known Size. Choose Mass or Weight to inspect either unit's Completed and Remaining values. Task count stays visible. With Total Size selected, Mass + Weight = Total Size below the plot shows Completed / total for each unit.

Lines connect saved observations. A Correction updates the opening plan without adding a scope jump on the day it was recorded. A Scope change changes the chart from the time it takes effect. Reopening Done work reduces Completed and increases Remaining from that point. Later live-task edits do not replace a Complete Sprint's saved outcomes; authorized Corrections and Exclude from metrics choices can change its reporting.

Hover over a data point to see values and the local time to the minute. Moving away hides the tooltip. You can also focus the chart and use the arrow keys. Expand Values & events for a table of observations, recorded events, Completed, Remaining, total scope, and estimate coverage. Dates and times use the current organization time zone. A longer Sprint has fewer date labels, but keeps every observation.

Missing estimates stay missing; zero is a known value. If some estimates are missing, Size uses the known ones and shows coverage. If all are missing, count can remain available while Size is unavailable. Empty or fully excluded scope has no completion percentage. When earlier task states are unknown, scope may be known while completion is unavailable. Current reporting refreshes every 30 seconds; Now is the latest successful observation.

Use Team Pulse to review work person by person. Planned and Current Sprints use current assignees and states. Complete Sprints show those saved at completion. Unknown user keeps unavailable profiles visible, and Unassigned always has its own row.

• Backlog combines Backlog and Queued work.
• Working combines Coding-agent Agent working and Person In progress work.
• Reviewing and Done show their corresponding task states.

Expand a person's row to see their tasks, or select a state count to show only matching tasks. All [person] tasks clears that person's state selection; All people clears the person selection. The same controls work for Unassigned. Select a task row to open its details, or use Open task in new tab within Team Pulse. On a Complete Sprint, the link opens today's task details while the row keeps its saved Sprint outcome.

The six overall cards show Backlog, Queued, Working, Reviewing, Done, and Closed separately. Select one to inspect matching tasks. Select it again or choose Clear state filter to reset. Sprint tasks below Team Pulse contains the full table. Closed tasks remain in the all-task lists even though Team Pulse has no separate Closed column.

Team Pulse and state cards include tasks marked Exclude from metrics, so their totals can be larger than the progress charts. Counts help find work; they do not measure individual performance. Use Reload task states if they cannot load.

Scroll to Sprint tasks to manage one task at a time. Team Leads and organization owners or admins with project access can change membership. Other members can read the table and task history.

1. Use Add or move a task to search by task number or title. Choose an unassigned task or one from another Planned Sprint. A task in another Current Sprint must be managed there first.
2. Choose one task to add or move it, or select Remove on a member row. Planned Sprint changes save immediately without classification.
3. For a Current Sprint, choose Correction or Scope change in Change intent, then select Confirm change. Cancel or Escape applies nothing.

• Correction means the task and its Size should count in the opening plan. This can include a task created after the Sprint started. The task keeps its real creation, state, and completion dates; before it existed, its completed contribution is zero. Unknown earlier states stay unavailable. Only managers can choose Correction.
• Scope change means a new decision to add, remove, or resize work now. It changes reporting from this change onward and keeps the opening plan.

Adding or removing membership leaves task state, estimates, assignee, dependencies, Plan, and Milestone unchanged. The table shows up to 20 tasks per page and shares the Plan table layout. Select a row to open task details; Planning links to its other enabled planning records. Managers also see Remove. Mass/Weight is read-only here; edit the task to change its live estimate. See Reset a task view for filters and column widths.

Complete pages keep saved outcomes even if a task later changes or becomes unavailable. Managers can use Remove on a saved row, or Correct retained membership to restore a task with proven earlier participation. Confirm Correction. This changes the saved report without adding current membership, reopening the Sprint, or changing the live task. Missing proof of opening membership or the task's final outcome prevents the correction.

If the record or your access changed, the save applies nothing. Review the refreshed context and choose the action and intent again. Use Reload task section when context cannot load. Re-enable Sprints in Project Settings before changing membership if the feature is off.

A manager can complete a Current Sprint at any time, including after its planned end.

1. Open the Sprint and select Complete Sprint beside Edit Sprint.
2. Review Completion date and time in the current organization zone. It defaults to the current server time. Keep it unchanged to preserve that exact instant, or choose a date, select Apply, and edit the hour and minute. An earlier completion must follow the start and be supported by saved task and membership history. A future or unsupported time is rejected.
3. Review unfinished tasks and Size. This includes tasks marked Exclude from metrics, because completion still affects them. Missing estimates are identified; partial Size includes only known estimates.
4. Select Complete Sprint to confirm, or Cancel or Escape to leave the Sprint as it is.

Completion saves the final task outcomes, clears every task's current Sprint membership, and returns unfinished active tasks to Backlog. Done stays Done and Closed stays Closed. Assignees, dependencies, Plan and Milestone membership, comments, and work/review history stay in place. Resetting a task can change progress in a Current Milestone that also contains it, but not that Milestone's membership or opening plan.

Completion does not accept reviews, stop an external agent, or move tasks into another Sprint. Old queued work cannot dispatch and superseded runs cannot submit late results. Use the normal queue or start action for further work.

A Complete page keeps the final Horizon, charts, objective, Team Pulse, task states, and saved outcomes. Later task edits, moves, reopening, or deletion do not replace them. Exclude from metrics still controls reporting; operational task lists include every member.

Saved unfinished work stays visible after tasks return to Backlog. For example, if five Size was unfinished and an authorized Correction establishes that only three belonged in the plan, the opening plan and final shortfall recalculate to three.

To correct a saved estimate, expand Sprint history, then Correct retained estimates. Select Correct estimate, change Retained Mass or Retained Weight, and select Save Correction. Blank means no estimate; zero means a known zero. This repairs the opening plan while keeping later Scope changes, the live task, and the completion time unchanged. Use the membership controls described above to correct saved participation. Ordinary Scope changes are unavailable after completion.

Sprint history lists changes newest first. Each collapsed row shows a short description and when it was recorded, down to seconds. Search or filter to find a change, then expand it for who made it, before/after values, and saved evidence or revisions. Effective time is when a change applies to the Sprint; recorded time is when it was saved. Both use the current organization zone. Corrections are available separately from the log. A task's metadata opens the same style of history for that task alone.

To undo completion, select Reopen Sprint and confirm the numbered dialog. It returns to Current and restores all members from its latest completion, including unfinished tasks returned to Backlog. Task states stay unchanged. Use the usual queue or start action to continue work. Completing it again saves a new final result without discarding the earlier completion.

Reopening is blocked if another Sprint is Current, a later Sprint would overlap, a former member was deleted, changed, or joined another Sprint, or history Corrections make restoration unsafe. No tasks are restored unless the whole action can succeed. Resolve the stated conflict, reload, and review again.

If the Sprint, tasks, settings, or your access changed, the action applies nothing. Use Reload Sprint when offered, then review and confirm again. Missing history must be resolved before a saved-outcome Correction can succeed. A failed action never silently retries completion.

Turning Sprints off hides their navigation, pages, task links, selectors, and filters. It keeps records, membership, dates, and history. A direct link shows an unavailable page; managers can open Project Settings and members can ask a Team Lead. Turning Sprints back on restores the same state, including an overdue Current Sprint. It does not change Milestones, Plans, or Metrics.

An estimate edit that affects saved Current Sprint history still needs a Planning history change choice in the browser. The CLI also supports classified Sprint estimate edits while disabled; Sprint assignment, clearing, and filters wait until the feature is enabled. See task changes and the CLI workflow.

Use Clear state filter to remove a state-card selection. In Team Pulse, use All people to clear the person selection or All [person] tasks to clear a person's state selection. These actions leave other filters alone.

Drag a table header's resize handle to make room, or focus it, press Enter, and use the arrow keys. Press Enter or Tab to finish. Widths are remembered in this browser. Reset column widths restores defaults without clearing task filters. You can also scroll horizontally to reach all enabled columns.

In Complete Sprint, you can choose a prepared following Sprint and confirm Complete and start Sprint #N. Choose ordinary Complete Sprint to finish without starting another.

The Current Sprint completes first. The selected Sprint then starts after a fresh check. If starting fails, completion stays saved. Review the explanation and retry or open the following Sprint; the completed Sprint is not reopened. Tasks are not automatically carried into the following Sprint.