Skip to content
This repository was archived by the owner on Jan 21, 2026. It is now read-only.

Commit 378cbe9

Browse files
committed
updating the 3-week sprint timings + explanation + screenshot
1 parent d2c0850 commit 378cbe9

2 files changed

Lines changed: 2 additions & 2 deletions

File tree

Instructions/Labs/AZ400_M01_L01_Agile_Planning_and_Portfolio_Management_with_Azure_Boards.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -92,9 +92,9 @@ Each new project is configured with a default team, which name matches the proje
9292

9393
![In the "interations" tab, click on "Edit"](images/m1/EShop-WEB-edit_iteration_v1.png)
9494

95-
> **Note**: Specify the Start Date as the first work day of last week, and specify Friday in 3 weeks from the Start Date as the End Date. This follows the best practice of having 3-week Sprints.
95+
> **Note**: Specify the Start Date as the first work day of last week, and count 3 full work weeks for each sprint. For example, if March 6 is the first work day of the sprint, it goes until March 24th. Sprint 2 starts on March 27, which is 3 weeks out from March 6.
9696

97-
1. Repeat the previous step to add **Sprint 2** and **Sprint 3**. The second sprint is our current iteration, reflecting the working days of the current week, and the third is reflecting the dates of next week.
97+
1. Repeat the previous step to add **Sprint 2** and **Sprint 3**. You could say that we are currently in the 2nd week of the first sprint.
9898

9999
![Do the same for Sprint 2 and 3, make sure they are created for "EShop-Web" team](images/m1/EShop-WEB-3sprints_v1.png)
100100

-5.35 KB
Loading

0 commit comments

Comments
 (0)