Manage sprint timelines
Azure DevOps Services | Azure DevOps Server 2020 | Azure DevOps Server 2019 | TFS 2018 - TFS 2013
With Scrum, teams plan and track work at regular time intervals, referred to as a sprint cadence. You define Iteration Paths, also referred to as sprints, to support the assignment of work items to time-box intervals. Iteration paths are a shared resource used by all teams that select them. Many teams choose a two or three week cadence. You can, however, specify shorter or longer sprint cycles. Or, you can create a release schedule that encompasses several sprints.
If all you need is to change the iteration dates, you can do that by following the guidance provided in this article. However, if you need to define the iteration paths and tree structure, or assign team sprints, then follow the guidance provided in Define iteration paths (sprints) and configure team iterations.
- To change sprint dates, you must be a member of the Project Administrators security group, or have the Edit this node permission for the iteration child node you want to change. By default, the user who created the project has these permissions set. To learn more, see Change project-level permissions or Set permissions and access for work tracking.
Start scheduling sprints
To quickly get started, you can use the default sprints. Default sprints are also referred to as iterations and were added when your project was created. Note, you must be a member of the Project Administrators group to add sprints and schedule sprint dates. If you created the project, you're a member.
That's it! You can now start planning your first sprint.
If you have several teams, more complex release and sprint cadences to schedule, or want to create child iterations, then read further. You define these items through the settings context for the project. See Define iteration (sprint) paths and configure team iterations.
Terminology note: Your set of Agile tools uses the Iteration Path field to track sprints and releases. When you define sprints, you define the picklist of values available for the Iteration Path field. You use iterations to group work into sprints, milestones, or releases in which they'll be worked on or shipped.
Schedule new sprints for different teams and release cadences
Your sprint backlog and taskboard are designed to support your Scrum processes. In addition, you have access to product and portfolio backlogs and Kanban boards. For an overview of the features supported on each backlog and board, see Backlogs, boards, and plans.
Your project comes with several sprints predefined. However, they aren't associated with any dates. For Scrum and sprint planning, you'll want to assign start and end dates for the sprints your team will use.
Defining other sprints is a two-step process. You first define the sprints for your project and then you select the sprints that each team will use—Define iteration (sprint) paths and configure team iterations. In this way, the system supports teams that work on different sprint cadences.
Each sprint that you select for your team provides access to a sprint backlog, taskboard, and other sprint planning tools for planning and tracking work.
For example, by selecting Sprints 1 through 6, the Fabrikam Fiber team gets access to six sprint backlogs. They also get access to capacity planning tools and a taskboard for each sprint.
If you work with several teams, and each team wants their own backlog view, you can create more teams. Each team then gets access to their own set of Agile tools. Each Agile tool filters work items. These items only include those assigned values under the team's default area path and iteration path.