Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Azure DevOps Services | Azure DevOps Server | Azure DevOps Server 2022 | Azure DevOps Server 2020
In the Scrum framework, teams plan and track work item assignments in regular time intervals called sprints. To use the Scrum and sprint planning cadence, you assign start and end dates for your team's sprints. This article describes how to set the iteration dates for sprints.
Agile tools use the Iteration path field to track sprints and releases. Iteration paths and sprints are shared resources by all the teams that use them. Teams can choose two or three-week cadences, but you can also specify shorter or longer sprint cycles or create a release schedule that encompasses several sprints.
Use the guidance in this article to set or change sprint dates. To define iteration paths and tree structure or associate teams with sprints, see Define iteration paths (sprints) and configure team iterations.
Prerequisites
| Category | Requirements |
|---|---|
| Permissions | To change sprint dates: Member of the Project Administrators group, or Edit this node permission for the iteration child node, which is the team name. By default, the user who created the project has these permissions. For more information, see Change project-level permissions or Set permissions and access for work tracking. |
Start scheduling sprints
Projects come with several predefined sprints that aren't associated with any dates. To quickly get started scheduling sprints, you can use the default sprints and assign start and end dates for your team's sprints.
In your Azure DevOps project, select Boards > Sprints from the left navigation menu. The Sprints page opens to your team's Taskboard view. Select the Backlog tab.
To select a different team, select the dropdown arrow next to the team name and choose a different team or View sprints directory from the selector.
At the top of the Backlog page, select Set dates.
On the Edit iteration screen, select the calendar icons to select the start date and end date, or enter them directly, and then select Save and close.
The Backlog page now shows the sprint dates, and you can start planning your first sprint.
Schedule sprints for other teams and releases
Defining sprints other than the defaults is a two-step process. First you define the sprints for your project, and then you select the sprints for each team to use. This system supports teams that work on different sprint cadences. For more information, see Define area paths and assign to a team.
When you define sprints, you define the picklist of values available for the Iteration path field to assign work to sprints, milestones, or releases. If you have several teams, releases, and sprint cadences to schedule, or to create child iterations, you can use Project Settings > Boards > Project configuration. The following screenshot shows the list of iterations for a project.
If you work with several teams and each team wants their own backlog view, you can create more teams. Each team gets access to their own set of Agile tools filtered to work items for that team's default area path and iteration path.
Each sprint selected for a team provides a backlog, board, and other planning and tracking tools for the team to use for that sprint. In the following example, the Management team has access to backlogs, capacity planning tools, and boards for several sprints. For more information, see Implement Scrum practices for your team in Azure Boards.
