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
{{ message }}
This repository was archived by the owner on Nov 14, 2025. It is now read-only.
Copy file name to clipboardExpand all lines: Instructions/Labs/AZ400_M01_L01_Agile_Plan_and_Portfolio_Management_with_Azure_Boards.md
+10-8Lines changed: 10 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,7 +65,7 @@ Each new project is configured with a default team, which name matches the proje
65
65
66
66
1. Click the cogwheel icon labeled **Project settings** located in the lower left corner of the page to open the **Project settings** page.
67
67
68
-

68
+

69
69
70
70
1. In the **General** section, select the **Teams** tab. There is already a default team in this project, **eShopOnWeb Team** but you'll create a new one for this lab. Click **New Team**.
71
71
@@ -143,13 +143,13 @@ Work items play a prominent role in Azure DevOps. Whether describing work to be
143
143
144
144

145
145
146
-
1. Click **Add link** to save the Child item.
146
+
1. Click **Add link** to save the Child item
147
147
148
148

149
149
150
150
> **Note**: On the **Training dashboard** panel, note that the assignment, **Area**, and **Iteration** are already set to the same values as the epic that the feature is based on. In addition, the feature is automatically linked to the parent item it was created from.
151
151
152
-
1. On the (New Feature) **Training dashboard** panel, click **Save & Close**.
152
+
1. On the (New Feature) **Training dashboard** panel, click **Save and Close**.
153
153
154
154
1. In the vertical navigation pane of the Azure DevOps portal, in the list of the **Boards** items, select **Boards**.
155
155
1. On the **Boards** panel, select the **EShop-WEB boards** entry. This will open the board for that particular team.
@@ -209,11 +209,11 @@ Work items play a prominent role in Azure DevOps. Whether describing work to be
209
209
1. At the top of the **NEW TASK** panel, in the **Enter title** textbox, type **`Add page for most recent tutorials`**.
210
210
1. On the **NEW TASK** panel, in the **Remaining Work** textbox, type **5**.
211
211
1. On the **NEW TASK** panel, in the **Activity** dropdown list, select **Development**.
212
-
1. On the **NEW TASK** panel, click **Save & Close**.
212
+
1. On the **NEW TASK** panel, click **Save and Close**.
213
213
214
214

215
215
216
-
1. Repeat the last five steps to add another task named **`Optimize data query for most recent tutorials`**. Set its **Remaining Work** to **3** and its **Activity** to **Design**. Click **Save & Close** once completed.
216
+
1. Repeat the last five steps to add another task named **`Optimize data query for most recent tutorials`**. Set its **Remaining Work** to **3** and its **Activity** to **Design**. Click **Save and Close** once completed.
217
217
218
218
#### Task 3: Manage sprints and capacity
219
219
@@ -279,9 +279,9 @@ The sprint backlog should contain all the information the team needs to successf
279
279
1. Click the **Configure team settings** cogwheel icon (directly to the right of the funnel icon).
280
280
1. On the **Settings** panel, select the **Styles** tab, click **+ Add styling rule**, under the **Rule name** label, in the **Name** textbox, type **`Development`**, and, in the **Color** dropdown list, select the green rectangle.
281
281
282
-
> **Note**: This will color all cards green if they meet the rule criteria set directly below, in the **Rule criteria** section.
282
+
> **Note**: This will color all cards green if they meet the rule criteria set directly belowthe rule name.
283
283
284
-
1. In the **Rule criteria** section, in the **Field** dropdown list, select **Activity**, in the **Operator** dropdown list, select **=**, and, in the **Value** dropdown list, select **Development**.
284
+
1. In the section under the rule name, in the **Field** dropdown list, select **Activity**, in the **Operator** dropdown list, select **=**, and, in the **Value** dropdown list, select **Development**.
285
285
286
286

287
287
@@ -337,7 +337,7 @@ To maximize a team's ability to consistently deliver high quality software, Kanb
337
337
1. From the detailed item view, at the top of the panel, to the right of the **0 comments** entry, click **Add tag**.
338
338
1. In the resulting textbox, type **`data`** and press the **Enter** key.
339
339
1. Repeat the previous step to add the **`ux`** tag.
340
-
1. Save these edits by clicking **Save & Close**.
340
+
1. Save these edits by clicking **Save and Close**.
341
341
342
342

343
343
@@ -428,7 +428,9 @@ Dashboards allow teams to visualize status and monitor progress across the proje
428
428
429
429
1. On the **Configuration** pane, click **Close** without making any changes.
430
430
1. Back on the **Add Widget** pane, in the **Search** textbox, type **`sprint`** again to find existing widgets that focus on sprints. In the list of results, select **Sprint Capacity** and click **Add**.
431
+
431
432
> **Note**: If the widget shows "Set capacity to use the sprint capacity widget", you can select the **Set capacity** link to set the capacity. Set the Activity to Development and the Capacity to 1. Click **Save** and back to the dashboard.
433
+
432
434
1. In the **Dashboard** view, at the top of the pane, click **Done Editing**.
433
435
434
436

0 commit comments