Skip to content

Latest commit

 

History

History
120 lines (75 loc) · 6.94 KB

scrum-process.md

File metadata and controls

120 lines (75 loc) · 6.94 KB
title titleSuffix ms.custom description ms.service ms.assetid ms.topic ms.author author monikerRange ms.date
Manage Scrum process template objects
Azure Boards
work-items
Learn how to use Scrum process objects to plan and track work and monitor progress and trends when you're connected to Azure DevOps.
azure-devops-boards
f4e77db3-e54c-472a-ba60-92ceb8331882
conceptual
chcomley
chcomley
<= azure-devops
06/07/2023

Manage Scrum process template objects

[!INCLUDE version-lt-eq-azure-devops]

The Scrum process supports the following work item types (WITs) to plan and track work, tests, feedback, and code review. With different WITs you can track different types of work—such as product backlog items, tasks, bugs, and more. These objects get created when you create a project using the Scrum process. They're based on Scrum principles and values.

:::image type="content" source="media/scrum-process-work-tracking-wits.png" alt-text="Conceptual image, Scrum process work item types.":::

Along with the WITs, teams have access to a set of work item queries to track information, analyze progress, and make decisions.

[!INCLUDE temp]

Plan and track work with Scrum processes

You build your project plan by creating a backlog of work items that represent the features, requirements, user stories, or other work to do. You track bugs, tasks, and blocking issues using the bug, task, and impediment WITs. To support portfolio management, teams create features and epics to view a rollup of their product backlog items within or across teams. For more information, see Scrum process work item types and workflow.

[!INCLUDE temp]

For more information, see Scrum work item types and workflow.

List work items

Define work item queries to list work items for a current sprint or the product backlog.

[!INCLUDE temp]

::: moniker range="tfs-2018"

Or, use the shared queries that the Scrum process provides.

:::image type="content" source="media/IC665405.png" alt-text="Screenshot of Shared queries for the Scrum process.":::

You can find descriptions of predefined queries later in this article.

Tip

Queries listed under the Current Iteration folder don't automatically update when a new iteration becomes current. The current iteration is based on the dates that you assign to your sprint schedules. You must manually update the iteration path of each query to have it point to the iteration path that corresponds to the current iteration. Or, you can edit the shared query to use the @CurrentIteration macro.

::: moniker-end

[!INCLUDE temp]

Monitor work progress

All processes—Agile, Scrum, and CMMI—support building status and trend charts and dashboards. Also, several charts are automatically built based on the Agile tools you use. These charts display within the web portal.

[!INCLUDE temp]

[!INCLUDE temp]

::: moniker range="< azure-devops-2022"

Scrum process and SQL Server reports

If your project collection and project are configured with SQL Server Analysis Services and Reporting Services, you have access to many Scrum reports. For these reports to be useful, teams must complete certain activities, such as define build processes, link work items, and update status or remaining work.

If you need to add reporting services or update reports to the latest versions, see Add reports to a project.

::: moniker-end

Scrum process versions

As updates get made to the Scrum process template, the version number gets updated. The following table provides a mapping of the versioning applied as updates get made to the Azure DevOps on-premises process templates. For Azure Boards, the latest version always gets used. Each template provides a version element, which specifies a major and minor version.

[!div class="mx-tdCol2BreakAll"]

Version Scrum process name Major version
Azure DevOps Services
Azure DevOps Server 2022		 Scrum 18
Azure DevOps Server 2020
Azure DevOps Server 2019		 Scrum 17
TFS 2018 Scrum 16

For a summary of updates made to process templates, see Release Notes for Azure DevOps Server.

::: moniker range="tfs-2018"

Scrum process predefined queries

Your product owner can plan and track product backlog items and bugs in the product backlog by using the Product Backlog query. You can find work items that are assigned to the current sprint by using the shared queries that are listed under the Current Sprint folder. These queries find work items that are assigned to a specified iteration or sprint. As you plan more sprints, you can modify these queries to specify the latest sprint and save them to other folders that you create, such as Sprint 2 or Sprint 3.

The project administrator for each project defines area paths and iteration paths for that project so that the team can track progress by those designations.

[!div class="mx-tdCol2BreakAll"]

Shared queries Description
Blocked Tasks Lists all tasks in the current sprint that have been marked as Blocked.
Open Impediments Lists all open impediment work items in the current sprint.
Sprint Backlog Lists all product backlog items, bugs, and their linked tasks that your team has committed to complete in the current sprint.
Test Cases Lists all test cases in the current sprint and sorts them by priority.
Unfinished Work Lists all product backlog items, bugs, and their linked tasks that have not been marked as Done in the current sprint.
Work in Progress Lists all tasks in the current sprint that are marked as In Progress.
Feedback Lists all feedback responses that are in an Active state.
Product Backlog Lists all product backlog items and bugs that are assigned to the root iteration. Product backlog items and bugs are sorted by backlog priority.

::: moniker-end

Related articles

[!INCLUDE temp]