You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
19
+
This article describes how to change the iteration dates for *sprints*. In the Scrum framework, teams plan and track work item assignments in regular time intervals called the sprint cadence.
20
20
21
-
> [!TIP]
22
-
> 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](../../organizations/settings/set-iteration-paths-sprints.md).
21
+
Iteration paths and sprints are shared resources by all the teams that select them. Many teams choose a two or three-week cadence, but you can specify shorter or longer sprint cycles or create a release schedule that encompasses several sprints.
22
+
23
+
You can change sprint dates by following the guidance in this article. To define the iteration paths and tree structure, or assign team sprints, see [Define iteration paths (sprints) and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md).
23
24
24
25
25
26
## Prerequisites
@@ -34,34 +35,25 @@ With Scrum, teams plan and track work at regular time intervals, referred to as
34
35
35
36
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, be a member of the [**Project Administrators** group](../../organizations/security/change-project-level-permissions.md) to add sprints and schedule sprint dates. If you created the project, you're a member.
36
37
37
-
::: moniker range=">= azure-devops-2020"
38
-
39
38
1. From your web browser, open your team's sprint backlog. (1) Check that you've selected the right project, (2) choose **Boards>Sprints**, (3) select the correct team from the team selector menu, and lastly (4), choose **Backlog**.
40
39
41
-
> [!div class="mx-imgBorder"]
42
-
> 
40
+

43
41
44
42
1. To choose another team, open the selector and select a different team or choose the :::image type="icon" source="../../media/icons/home-icon.png" border="false"::: **Browse all sprints** option. Or, you can enter a keyword in the search box to filter the list of team backlogs for the project.
45
43
46
-
> [!div class="mx-imgBorder"]
47
-
> 
44
+

3. Choose the calendar icon to select the start date, and then the end date of the sprint.
50
+
1. Choose the calendar icon to select the start date, and then the end date of the sprint.
55
51
56
-
> [!div class="mx-imgBorder"]
57
-
> 
52
+

58
53
59
-
4. Choose **Save and close**. You'll see the date listed.
54
+
1. Choose **Save and close**. You'll see the date listed.
60
55
61
-
> [!div class="mx-imgBorder"]
62
-
> 
63
-
64
-
::: moniker-end
56
+

65
57
66
58
That's it! You can now start [planning your first sprint](assign-work-sprint.md).
67
59
@@ -70,12 +62,11 @@ If you have several teams, more complex release and sprint cadences to schedule,
70
62
> [!NOTE]
71
63
> **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](../../organizations/settings/set-area-paths.md) field. You use iterations to group work into sprints, milestones, or releases in which they'll be worked on or shipped.
72
64
73
-
<aid="schedule"> </a>
74
-
65
+
<aid="schedule"></a>
75
66
## Schedule new sprints for different teams and release cadences
76
67
77
-
> [!NOTE]
78
-
> Your sprint backlog and taskboard are designed to support your Scrum processes. In addition, you have access to product and portfolio backlogs and boards. For an overview of the features supported on each backlog and board, see [Backlogs, boards, and plans](../backlogs/backlogs-boards-plans.md).
68
+
> [!NOTE]
69
+
> Your sprint backlog and taskboard are designed to support your Scrum processes. In addition, you have access to product and portfolio backlogs and boards. For an overview of the features supported on each backlog and board, see .
79
70
80
71
Your project comes with several sprints predefined. However, they aren't associated with any dates. For Scrum and sprint planning, assign start and end dates for your team's sprints.
81
72
@@ -96,8 +87,12 @@ For example, by selecting Sprints 1 through 6, the Fabrikam Fiber team gets acce
96
87
## Next step
97
88
98
89
> [!div class="nextstepaction"]
99
-
> [Assign work to a sprint](assign-work-sprint.md) or [Define iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md)
90
+
> [Assign work to a sprint](assign-work-sprint.md)
100
91
101
92
## Related content
102
93
103
-
If you work with several teams, and each team wants their own backlog view, you can [create more teams](../../organizations/settings/add-teams.md). 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.
94
+
-[Define iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md)
95
+
-[Create more teams](../../organizations/settings/add-teams.md)
96
+
-[Backlogs, boards, and plans](../backlogs/backlogs-boards-plans.md)
97
+
98
+
If you work with several teams, and each team wants their own backlog view, you can . 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.
0 commit comments