Plan and run a sprint

Organize project work into a time-boxed sprint, track it as the team executes, and carry unfinished work into the next cycle.

Sprints group tasks into a focused, time-boxed cycle so a team commits to a set of work, executes it, and reviews the result. This guide runs one sprint end to end.

1. Create the sprint

Create a sprint on the project and give it a name and a start and end date. The date range defines the cycle the team is committing to.

A sprint groups tasks into a time-boxed cycle

2. Add tasks to the sprint

Pull the tasks the team will tackle into the sprint. You can assign each task an owner and a time estimate so the planned workload is visible before the cycle begins. Tasks that aren't ready can stay out and be added to a later sprint.

3. Start the sprint

Starting the sprint marks the cycle as active. From here the sprint becomes the team's working set, and you can filter any task view down to just this sprint's work.

4. Track progress

Follow the work as it moves using whichever view suits the team:

• Kanban View—drag tasks across status columns to see flow at a glance.
• List View—a sortable table for detailed tracking and bulk updates.

Kanban and list views of the sprint's tasks

Filter by sprint to keep the board focused on the current cycle. A Calendar View is also available for date-based planning across the cycle.

Calendar view for date-based planning

To see where these views live on screen, see the Project Suite screens.

5. Complete the sprint

When the cycle ends, complete the sprint. Work that was finished is captured with the closed sprint; incomplete tasks can be carried over into the next sprint so nothing is lost between cycles.

6. Review and plan the next cycle

Use the completed sprint to review what shipped and what rolled over, then start the next sprint with the carried-over work already in place.

For what statuses, estimates, and story points mean, see the Projects & Tasks reference.