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
Scrum methods use *iteration paths*, or *sprints*, to plan work for a team within a specific time period and cadence. Useful tools for implementing Scrum practices in Azure Boards include filtered backlogs and boards based on iteration paths. You can use Scrum to schedule and plan sprints, update your board, and monitor sprint burndown.
19
+
Scrum methods use *iteration paths*, or *sprints*, to plan work for teams within specific time periods and cadences. Useful tools for implementing Scrum practices in Azure Boards include filtered backlogs and boards based on iteration paths. You can use Scrum to schedule and plan sprints, update your board, and monitor sprint burndown.
20
20
21
-
For an introduction to Scrum, see [What is Scrum](/devops/plan/what-is-scrum).
You can quickly assign work items to a sprint by dragging and dropping them from the project backlog to the sprint. To get started with Scrum, you can use the default sprints that are predefined for each project.
41
+
### Assign backlog items to sprints
42
+
43
+
You can quickly assign work items to a sprint by dragging and dropping them from the product backlog to the sprint. To get started with Scrum, you can use the default sprints that are predefined for each Azure DevOps project.
44
44
45
45
1.[Assign backlog items to a sprint](assign-work-sprint.md).
46
46
1.[Add tasks to backlog items](add-tasks.md).
47
47
1.[Set sprint capacity](set-capacity.md).
48
48
1.[Adjust work to fit sprint capacity](adjust-work.md).
@@ -59,9 +62,9 @@ You can quickly assign work items to a sprint by dragging and dropping them from
59
62
60
63
Sprint backlogs and boards provide filtered views of work items for teams assigned to specific iteration paths or sprints. Sprints are defined for a project and then selected for teams.
61
64
62
-
From the team backlog, you can map work to an iteration path using drag-and-drop, and then view the work for each iteration path in a separate sprint backlog. The sprint backlog contains a filtered subset of backlog items whose iteration path corresponds to the chosen sprint.
65
+
From the team backlog, you can map work to an iteration path using drag-and-drop, and then view the work for each iteration path in a separate backlog. The sprint backlog contains a filtered subset of backlog items whose iteration path corresponds to the chosen sprint.
63
66
64
-
67
+
:::image type="content" source="../work-items/media/view-add/view-sprint-backlogs.png" alt-text="Screenshot of a sprint backlog.":::
65
68
66
69
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 that filter work items to the team's default area path and iteration path.
67
70
@@ -70,28 +73,26 @@ If you work with several teams and each team wants their own backlog view, you c
70
73
71
74
Each sprint you select for your team provides access to a sprint backlog, board, and other Agile tools for planning and tracking work. The **Planning** view provides an overview of your sprint planning.
72
75
73
-
From the project backlog or any sprint backlog, select the **View options** icon and then select **Planning**. The sprints selected for your team appear in a side pane.
76
+
From the project backlog or any sprint backlog page, select the **View options** icon and then select **Planning**. The sprints selected for your team appear in a side pane.
77
+
78
+
To select a sprint backlog, you can choose one of the sprint links from the **Planning** pane, or you can choose it from the sprint selector on a sprint backlog page.
74
79
75
-
80
+
:::image type="content" source="media/overview/select-a-sprint-new-nav.png" alt-text="Screenshot showing how to select a sprint.":::
76
81
77
-
If no sprints are listed, you can add sprints or select existing sprints for your team. For more information, see [Define sprints](define-sprints.md).
82
+
If no sprints are listed in the **Planning** pane or sprint dropdown list, you can add sprints or select existing sprints for your team. For more information, see [Define sprints](define-sprints.md).
78
83
79
84
> [!NOTE]
80
85
> The Planning pane shows only the current sprint and the next 10 future sprints, even if the team has more sprints selected.
81
86
82
-
To select a sprint backlog, you can choose one of the sprint links from the **Planning** pane. You can also choose a different sprint from the sprint selector on a sprint backlog page.
83
-
84
-
85
-
86
87
## Capacity tracking
87
88
88
-
Once you [define iteration paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md), you can start using Agile capacity planning tools to plan the work your team can commit to. The capacity planning and capacity bar tools support this task.
89
+
Once you [define iteration paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md), you can start using Agile capacity planning tools to plan the work your team can commit to during a sprint. The capacity planning and capacity bar tools support this task.
89
90
90
91
### Capacity planning tool
91
92
92
93
Use the team capacity tool under the **Capacity** tab to set individual team member capacity and days off, and holidays or shared days off for the entire team. When you set team capacity, the team knows the exact total number of work hours or days they have for each sprint. For more information, see [Set capacity for the team and team members](set-capacity.md#set-capacity-for-the-team-and-team-members).
93
94
94
-
95
+
:::image type="content" source="media/team-capacity-planning-tool.png" alt-text="Screenshot of Team capacity planning tool.":::
95
96
96
97
### Capacity bars
97
98
@@ -105,55 +106,55 @@ Capacity bars update with each of these activities:
105
106
- Remaining work changes.
106
107
- Dates change within the sprint cycle.
107
108
108
-
109
+
:::image type="content" source="media/overview/capacity-bars.png" alt-text="Screenshot of capacity bars.":::
109
110
110
111
## Task board and burndown chart
111
112
112
-
During a sprint, you can use the taskboard and sprint burndown chart to track progress. The sprint burndown chart provides an at-a-glance visual to determine if your team is on track to meet its sprint plan.
113
+
During a sprint, you can use the task board and sprint burndown chart to track progress. The sprint burndown chart provides an at-a-glance visual to determine if your team is on track to meet its sprint plan.
113
114
114
115
Your [task board](task-board.md) provides an interactive progress record for work required to complete the sprint backlog. During your sprint, update the status of tasks and the remaining work for each task. Updating tasks daily or several times a week yields a smoother burndown chart.
115
116
116
-
117
+
:::image type="content" source="media/overview/board.png" alt-text="Screenshot of Taskboard.":::
117
118
118
119
The [sprint burndown chart](../../report/dashboards/configure-sprint-burndown.md) reflects progress by your team in completing the work they estimated during planning. Use the burndown chart to help mitigate risk and check for scope creep throughout the sprint cycle.
119
120
120
121
On the burndown chart, the ideal trend line always indicates a steady burndown, while the blue area represents what's actually occurring. This area shows the buildup of work as team members add tasks and the reduction of work as team members complete their tasks.
121
122
122
-
123
+
:::image type="content" source="media/overview/chart.png" alt-text="Screenshot of Sprint burndown chart.":::
123
124
124
125
<aid="velocity-forecast"> </a>
125
126
## Velocity and forecast tools
126
127
127
128
After several sprints, you can use the [Velocity chart](../../report/dashboards/team-velocity.md) and [Forecast tool](forecast.md) to help estimate work your team can complete in future sprints.
128
129
129
-
Velocity is a useful metric for gaining insight into how much work your team completes during a sprint cycle. Each team is associated with one velocity chart. You can select the **Velocity** chart on the **Analytics** tab of the team **Backlog** page.
130
+
Velocity is a useful metric for gaining insight into how much work your team completes during a sprint cycle. Each team is associated with one velocity chart.
130
131
131
-
The green bar within the chart indicates the total estimated effort, based on story points or size of backlog items, such as user stories or requirements, completed within the sprint. The light blue area corresponds to the estimated effort of items not yet completed.
132
+
Select the **Velocity** chart on the **Analytics** tab of the team **Backlog** page. In the chart, the green bar indicates total estimated effort, based on story points or size of work items completed within the sprint. The light blue area corresponds to the estimated effort of items not yet completed.
132
133
133
-
134
+
:::image type="content" source="media/velocity-chart.png" alt-text="Screenshot of Velocity chart.":::
134
135
135
136
Velocity varies depending on team capacity over sprints, but over time should be a reliable average you can use to forecast against the full backlog. To get more reliable velocity metrics, minimize the variability of backlog item sizes, effort, and story points.
136
137
137
-
The forecast tool helps determine how much work your team can complete within a sprint, given a specified team velocity. On the team **Backlog** page, select the **View options** icon and then setting**Forecasting** to **On**.
138
+
The forecast tool helps determine how much work your team can complete within a sprint, given a specified team velocity. On the team **Backlog** page, select the **View options** icon and then set**Forecasting** to **On**.
138
139
139
-
Use the forecast tool to get an idea of how many and which items you can complete within a sprint. By setting a velocity, you can see which items are within scope for the set of sprints the team selected. In the following example, setting a velocity of 13 indicates that it takes three sprints to complete the work shown.
140
+
Use the forecast tool to get an idea of how many and which items you can complete within a sprint. By setting a velocity, you can see which items are within scope for the set of sprints the team selected. In the following example, setting a velocity of *15* indicates that it takes three sprints to complete the work shown.
140
141
141
-
142
+
:::image type="content" source="media/forecast-tool.png" alt-text="Screenshot of Forecast tool.":::
142
143
143
144
<aid="sprint-scope-change"></a>
144
145
## Sprint scope changes
145
146
146
147
There's no sprint scope change chart or widget, but the burndown chart shows the **Total Scope Increase** at upper right. You can also query for work items added to or removed from a sprint after its start.
147
148
148
-
### Query for work items added or removed after the start of the sprint
149
+
### Query for work items added or removed after sprint start
149
150
150
151
1. On the team backlog [velocity chart](../../report/dashboards/team-velocity.md) or the velocity chart widget, select the **Planned** bar for the sprint you're interested in.
151
152
152
153
1. The Query **Results** page opens, showing the list of work items defined for the sprint on its first day.
153
154
154
-
1. Select **Editor** to edit the query, and on the **Editor** page, change the query as follows.
155
+
1. Select the **Editor** tab to edit the query, and on the **Editor** page, change the query as follows.
155
156
156
-
To change the query to list work items added to the sprint after its start:
157
+
To list work items added to the sprint after its start:
157
158
158
159
- Change the operator for the **ID** field to **Not In**.
159
160
- Insert a clause at the top of the query to specify **In** for the **Work Item Types** you're interested in.
@@ -164,7 +165,7 @@ There's no sprint scope change chart or widget, but the burndown chart shows the
164
165
165
166
:::image type="content" source="media/overview/query-for-added-work-items-to-sprint.png" alt-text="Screenshot of a query for work items added to a sprint after its start.":::
166
167
167
-
To change the query to list work items that were moved out of the sprint after its start:
168
+
To list work items moved out of the sprint after its start:
168
169
169
170
- Insert a clause at the top of the query to specify **In** for the **Work Item Types** you're interested in.
170
171
- Add an **Under** clause for the team's **Area Path**.
0 commit comments