SkopoSign in
Browse the docs

Run a sprint

Plan, start, track, and close a Scrum sprint with the Sprint Board, the Product Backlog, and the sprint API.

The Sprint Board gives your Scrum team a focused view of the work committed for the current sprint, with a live burndown and per-column point totals.

Before you start

  • Sprints are available on projects using the Scrum methodology, and on Scrumban projects that turn on the Sprint goals practice. Other methodologies plan through the Backlog view without sprints.
  • A new Scrum project starts with two sprints, Sprint 1 and Sprint 2, sized from the sprint length and capacity you chose when creating the project.
  • Creating, editing, starting, and completing sprints is done through the MCP tools (create_sprint, update_sprint, start_sprint, complete_sprint) or the REST API. There are no sprint buttons in the app yet. You need the Lead project role or the workspace Owner role.

Plan the sprint

  1. Hold Sprint Planning (see /docs/guides/run-a-ceremony) to agree on a Sprint Goal.
  2. If you need another sprint, ask your AI assistant to call create_sprint with a name, goal, start and end dates, and capacity. Use update_sprint to change any of these before the sprint is completed.
  3. Open Product Backlog and drag items from Unscheduled Work into the sprint group. You can also set sprintId on a work item through MCP or the REST API.

Start the sprint

A sprint becomes active when its start date arrives. To start it on a different day, call start_sprint: it sets the start date to today and keeps the planned end date, or uses the project's sprint length if no end date is set. Only one sprint can be active at a time, so complete the current sprint first.

Track the sprint

  1. Open your Scrum project and click Sprint Board in the project sidebar.
  2. The board header shows the sprint name, its status badge (Active or Planned), the date range, days remaining, and the sprint goal. If no sprint is active, the board shows the next planned sprint.
  3. The header also shows three key metrics: Committed (total points selected for the sprint), Completed (points in Done), and Remaining (points not yet done). A live burndown chart on the right compares actual progress to the ideal line.
  4. Below the header, four columns show your sprint work: To Do, In Progress, In Review, and Done. Each column header shows item count and total points.
  5. Click any card to open the detail drawer and update the item, add comments, or link a pull request.
  6. Drag a card to another column to advance or revert its status. The burndown chart updates as items move to Done.

Close the sprint

  1. Run the Sprint Review and Sprint Retrospective from Scrum Events, completing each with Complete with outcomes (see /docs/guides/run-a-ceremony). Completing these sessions records outcomes; it does not close the sprint.
  2. Call complete_sprint with the sprint's id and a rolloverSprintId. Items in Done stay with the completed sprint. Unfinished items move to the sprint you name, or back to the backlog if you pass null. Each moved item gets a note in its activity.
  3. If the sprint finishes early, its end date becomes today. A completed sprint can no longer be edited.

Result

Your team has a focused view of sprint-committed work with a live burndown, and each completed sprint keeps its finished items while unfinished work moves to the sprint or backlog you chose.