draft

Author: v-thepet

docs/boards/sprints/define-sprints.md

@@ -1,7 +1,7 @@
 ---
-title: Manage sprint timelines while working in Scrum
-titleSuffix: Azure Boards  
-description: Learn how to add and set dates for sprints, releases, or iterations to implement Scrum in Azure Boards. 
+title: Manage sprint timelines
+titleSuffix: Azure Boards
+description: Learn how to set and add dates for sprints, releases, or iterations to implement Scrum in Azure Boards.
 ms.custom: boards-sprints
 ms.service: azure-devops-boards
 ms.assetid: 1DB81E71-36D7-43A5-9C9A-38AA1777715A
@@ -10,79 +10,66 @@ author: chcomley
 ms.topic: quickstart
 monikerRange: '<= azure-devops'
 ms.date: 10/27/2025
+#customer intent: As an Azure Boards project administrator, I want to set dates and assign teams to sprints and iterations so I can assign teams their own boards and backlogs to manage.
 ---
 
 # Manage sprint timelines 
 
 [!INCLUDE [version-lt-eq-azure-devops](../../includes/version-lt-eq-azure-devops.md)] 
 
-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.
+In the Scrum framework, teams plan and track work item assignments in regular time intervals called *sprints*. To use the Scrum and sprint planning cadence, you assign start and end dates for your team's sprints. This article describes how to set the iteration dates for sprints.
 
-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.
+Agile tools use the **Iteration path** field to track sprints and releases. Iteration paths and sprints are shared resources by all the teams that use them. Teams can choose a two or three-week cadence, but you can also specify shorter or longer sprint cycles or create a release schedule that encompasses several sprints.
 
-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).
- 
+Use the guidance in this article to set or change sprint dates. To define iteration paths and tree structure or associate teams with sprints, see [Define iteration paths (sprints) and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md).
 
 ## Prerequisites
 
 | Category | Requirements |
 |--------------|-------------|
-| **Permissions** | To change sprint dates: Member of the [**Project Administrators** group](../../organizations/security/change-project-level-permissions.md), or **Edit this node** permission for the iteration child node you want to change. By default, the user who created the project has these permissions set. For more information, see [Change project-level permissions](../../organizations/security/change-project-level-permissions.md) or [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md). | 
+| **Permissions** | To change sprint dates: Member of the [Project Administrators](../../organizations/security/change-project-level-permissions.md) group, or **Edit this node** permission for the iteration child node, which is the team name. By default, the user who created the project has these permissions. For more information, see [Change project-level permissions](../../organizations/security/change-project-level-permissions.md) or [Set permissions and access for work tracking](../../organizations/security/set-permissions-access-work-tracking.md). | 
 
 <a id="quick-start-schedule">   </a>
-
 ## Start scheduling sprints
 
-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. 
-
-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**. 
-
-   ![Open Work, Sprints, for a team](media/add-tasks/open-sprint-backlog-s155-co.png)
-
-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.
-
-   ![Choose another team](media/add-tasks/team-selector-sprints-agile.png) 
+Projects come with several predefined sprints that aren't associated with any dates. To quickly get started scheduling sprints, you can use these default sprints to assign start and end dates for your team's sprints.
 
-1. Choose **Set sprint dates**.  
+1. In your Azure DevOps project, select **Boards** > **Sprints** from the left navigation menu. The **Sprints** page opens to your team's **Taskboard** view. Select the **Backlogs** tab.
 
-   ![Boards>Sprints>set dates](media/define-sprints/set-sprint-dates-scrum-agile.png)
+   :::image type="content" source="media/define-sprints/open-sprint-backlog.png" alt-text="Screenshot that shows opening the Backlog tab of the Sprint page for a team.":::
 
-1. Choose the calendar icon to select the start date, and then the end date of the sprint. 
+1. To select a different team, select the dropdown arrow next to the team name and choose a different team or **View sprints directory** from the selector.
 
-   ![Edit iteration dialog, Set dates](media/define-sprints/edit-iteration-set-sprint-dates.png) 
+   :::image type="content" source="media/define-sprints/set-sprint-dates-scrum-agile.png" alt-text="Screenshot that shows the selector for choosing another team.":::
 
-1. Choose **Save and close**. You'll see the date listed. 
+1. At the top of the **Backlogs** page, select **Set dates**.
 
-   ![Boards>Sprints>Sprint dates set ](media/define-sprints/sprint-dates-set-scrum-agile.png)
+1. On the **Edit iteration** screen, select the calendar icons to select the start date and end date, or enter them directly, and then select **Save and close**.
 
-That's it! You can now start [planning your first sprint](assign-work-sprint.md). 
+   :::image type="content" source="media/define-sprints/edit-iteration-set-sprint-dates.png) " alt-text="Screenshot that shows the Edit iteration screen.":::
 
-If you have several teams, more complex release and sprint cadences to schedule, or want to create child iterations, then read further. You define these items through the settings context for the project. See [Define iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md). 
+The **Backlogs** page now shows the sprint dates, and you can start [planning your first sprint](assign-work-sprint.md).
 
-> [!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 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. 
+:::image type="content" source="media/define-sprints/sprint-dates-set-scrum-agile.png" alt-text="Screenshot that shows Sprint dates set.":::
 
 <a id="schedule"></a>
-## Schedule new sprints for different 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 boards. For an overview of the features supported on each backlog and board, see .  
+## Schedule sprints for other teams and releases
 
-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.
+Defining sprints other than the default sprints is a two-step process. First you [define the sprints for your project](../../organizations/settings/set-area-paths.md), and then you [select the sprints for each team to use](../../organizations/settings/set-iteration-paths-sprints.md). This system supports teams that work on different sprint cadences. For more information, see [Define area paths and assign to a team](../../organizations/settings/set-area-paths.md).
 
-Defining other sprints is a two-step process. You first define the sprints for your project and then you select the sprints for each team to use&mdash;[Define iteration (sprint) paths and configure team iterations](../../organizations/settings/set-iteration-paths-sprints.md). In this way, the system supports teams that work on different sprint cadences.  
+:::image type="content" source="media/define-sprints-project-level.png" alt-text="Diagram that shows defining project sprints." border="false"::: :::image type="content" source="media/define-sprints-team-level.png" alt-text="Diagram that shows selecting team sprints." border="false":::
 
-[![Define project sprints](media/define-sprints-project-level.png)](../../organizations/settings/set-area-paths.md)[![Select team sprints](media/define-sprints-team-level.png)](../../organizations/settings/set-iteration-paths-sprints.md)
+When you define sprints, you define the picklist of values available for the **Iteration path** field to assign work to sprints, milestones, or releases. If you have several teams, releases, and sprint cadences to schedule, or to create child iterations, you can use the project settings.
 
-Each sprint that you select for your team provides access to a [sprint backlog, taskboard, and other sprint planning tools](scrum-overview.md) for planning and tracking work. 
+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 gets access to their own set of Agile tools filtered to work items for that team's default area path and iteration path.
 
-For example, by selecting Sprints 1 through 6, the Fabrikam Fiber team gets access to six sprint backlogs. They also get access to capacity planning tools and a taskboard for each sprint. 
+The following screenshot shows the list of iterations for a project in **Project Settings** > **Boards**.
 
-::: moniker range="<=azure-devops"
+:::image type="content" source="media/define-sprints/set-sprint-dates.png" alt-text="Screenshot that shows sprints for a team in Project Settings.":::
 
-![Selected sprints for a team](media/define-sprints/selected-team-iterations-agile.png)
+Each sprint selected for a team gives that team a sprint backlog, taskboard, and other sprint planning and tracking tools to use. In the following example, the **Management** team has access to a sprint backlog, capacity planning tool, and taskboard for each of their sprints. For more information, see [Implement Scrum practices for your team in Azure Boards](scrum-overview.md).
 
-::: moniker-end
+:::image type="content" source="media/define-sprints/selected-team-iterations-agile.png" alt-text="Screenshot that shows selected sprints for a team in Backlogs.":::
 
 ## Next step
 
@@ -95,4 +82,3 @@ For example, by selecting Sprints 1 through 6, the Fabrikam Fiber team gets acce
 - [Create more teams](../../organizations/settings/add-teams.md)
 - [Backlogs, boards, and plans](../backlogs/backlogs-boards-plans.md)
 
-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.