Azure Boards | Azure DevOps Server 2019 | TFS 2018 | TFS 2017 | TFS 2015 | TFS 2013
With Scrum, teams plan and track work at regular time intervals, referred to as a sprint cadence. You define sprints to correspond to the cadence your team uses.
Many teams choose a two or three week cadence. However, you can specify shorter or longer sprint cycles. Also, you can create a release schedule which encompasses several sprints.
- You must connect to a project. If you don't have a project yet, create one.
- To modify work tracking project configuration, you must be granted Stakeholder access or higher. For details, see About access levels.
- You must be added to a project as a member of the Project Administrators security group. To get added, see Set permissions at the project- or collection-level.
- Or, to add, edit, and manage Iteration Paths under a node, you must have one or more of the following permissions set to Allow for the node you want to manage: Create child nodes, Delete this node, and Edit this node, and View permissions for this node. By default, the user who created the project has these permissions set. To learn more, see Set permissions and access for work tracking.
Quick start guide to scheduling sprints
To quickly get started, you can use the default sprints, also referred to as iterations, that were added when your project was created. Note, you must be a member of the Project Administrators group in order to add sprints and schedule sprint dates. (If you created the project, you're a member.)
Your web portal uses either the New navigation or Previous navigation user interface. Choose the New navigation tab if the New Navigation feature is enabled. You'll see a vertical sidebar along with other navigational features when New Navigation has been enabled for the signed-in user or the organization. Choose Previous navigation when you see a top-level, blue-bar—indicating that New navigation isn't enabled. For more information, see Web portal navigation.
Choose the New navigation tab for guidance. Azure DevOps Server 2019 supports the New Navigation user interface. For more information, see Web portal navigation.
Choose the Previous navigation tab for guidance. TFS 2018 and earlier versions only support the previous navigation user interface. For more information, see Web portal navigation.
That's it! You can now start planning your first sprint.
Of course, if you have several teams, more complex release and sprint cadences to schedule, or want to create child iterations, then you'll need to read further. You define these through the settings context for the project.
Terminology note: Your set of Agile tools uses the Iteration Path field to track sprints and releases. When you define sprints, you define the pick list 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.
Add and schedule new sprints for several 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 additional 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 paths (aka sprints) 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 thru 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.
Try this next
If you work with several teams, and each team wants their own backlog view, you can create additional teams. Each team then gets access to their own set of Agile tools. Each Agile tool filters work items to only include those assigned values under the team's[default area path and iteration path.