Schedule sprints

VSTS | 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.

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.)

Note

Choose Previous navigation when you see a top-level blue bar. Choose New navigation if you see a vertical sidebar or if you enabled the New Navigation preview feature. The vertical sidebar, along with other navigational features, is enabled when the New Navigation preview feature has been enabled for the signed-in user or the VSTS organization. To learn how to use the web portal effectively, see Navigation Basics.

For on-premises TFS users, choose Previous Navigation for guidance.

  1. From your web browser, open your team's sprint backlog. (1) Check that you have selected the right project, (2) choose Work>Sprints, (3) select the correct team from the team selector menu, and lastly (4), choose Backlog.

    Open Work, Sprints, for a team

  2. To choose another team, open the selector and select a different team or choose the home-icon Browse all sprints option. Or, you can enter a keyword in the search box to filter the list of team backlogs for the project.

    Choose another team

  3. Choose Set sprint dates.

    Work>Sprints>set dates

  4. Choose the calendar icon to select the start date, and then the end date of the sprint.

    Edit iteration dialog, Set dates

  5. Choose Save and close. You'll see the date listed.

    New Navigation, Work>Sprints>Sprint dates set

New navigation isn't supported on TFS at this time. Choose Previous navigation for guidance.

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.

Note

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

Note

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—Define project iterations—and then you select the sprints that each team will use—Select team sprints. In this way, the system supports teams that work on different sprint cadences.

Define project sprintsSelect team sprints

Each sprint that you select for your team provides access to a sprint backlog, task board, 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 task board for each sprint.

Selected sprints for a team

New navigation isn't supported on TFS at this time. Choose Previous navigation for guidance.

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.