Default processes and process templates

Azure DevOps Services | Azure DevOps Server 2022 - Azure DevOps Server 2019

Azure Boards offers various processes for managing work items. Selecting the right process helps optimize project workflow and ensure your project's success. In this article, explore the different processes available with Azure Boards. This article provides guidance on how to choose the most suitable process for your project.

When you create a project, you choose a process or process template based on the process model for which your organization or collection was created. Before you choose a process for your project, you should understand the following terms.

The default process types are Basic, Agile, Capability Maturity Model Integration (CMMI), and Scrum. The work tracking objects in the default processes and process templates are the same. They're summarized in this article.

The default processes differ mainly in the work item types they provide for planning and tracking work. The default processes are:

• Basic: Is the most lightweight and is in a selective preview.
• Scrum: Is the next most lightweight.
• Agile: Supports many Agile method terms.
• CMMI: Provides the most support for formal processes and change management.

If you need more than two or three backlog levels, add more based on the process model that you use:

• Inheritance: Customize your backlogs or boards for a process
• Hosted XML or On-premises XML: Add portfolio backlogs

The default processes are designed to meet the needs of most teams. If your team has unusual needs and connects to an on-premises server, customize a process and then create the project. You can also create a project from a process and then customize the project.

The following table summarizes the main distinctions between the work item types and states used by the four default processes.

Notes:

1. Add work items from the product backlog or board. The product backlog shows a single view of the current backlog of work that can be dynamically reordered and grouped. Product owners can prioritize work and outline dependencies and relationships. Each team can configure how they want bugs to show up on their backlogs and boards.
2. Define a hierarchy of portfolio backlogs to understand the scope of work across several teams and see how that work rolls up into broader initiatives. Each team configures which portfolio backlogs appear for their use.
3. Define tasks from the sprint backlog and taskboard. With capacity planning, teams can determine if they're over capacity or under capacity for a sprint.

Workflow states support tracking the status of work as it moves from a New state to a Closed or a Done state. Each workflow consists of a set of states, the valid transitions between the states, and the reasons for transitioning the work item to the selected state.

The following diagrams show the typical forward progression of those work item types used to track work and code defects for the three default processes. They also show some of the regressions to former states and transitions to removed states.

Each image shows only the default reason associated with the transition.

Most work item types used by Agile tools, the ones that appear on backlogs and boards, support any-to-any transitions. Update the status of a work item by using the board or the taskboard. Drag a work item to its corresponding state column.

Change the workflow to support other states, transitions, and reasons. For more information, see Customize your work tracking experience.

When you change the state of a work item to Removed, Closed, or Done, the system responds as follows:

• Closed or Done: Work items in this state don't appear on the portfolio backlog and backlog pages. They do appear on the sprint backlog pages, board, and taskboard. When you change the portfolio backlog view to Show backlog items, for example, to view features to product backlog items, work items in the Closed and Done state appear.
• Removed: Work items in this state don't appear on any backlog or board.

Your project maintains work items as long as the project is active. Even if you set work items to Closed, Done, or Removed, the data store keeps a record. Use a record to create queries or reports.

If you need to permanently delete work items, see Remove or delete work items.

The following work item types are added to all processes except the Basic process.

Your team can create and work with these types by using the corresponding tool.

Work items from these type definitions aren't meant to be created manually and are then added to the Hidden Types category. Work item types added to the Hidden Types category don't appear on the menus that create new work items.

Work item types that support the test experience and work with Test Manager and the web portal are linked together by using the link types shown in the following image.

From the web portal or Microsoft Test Manager, view which test cases are defined for a test suite and view which test suites are defined for a test plan. However, these objects aren't connected to each other through link types. Customize these work item types as you would any other work item types. For more information, see Customize your work tracking experience.

If you change the workflow for the test plan and test suite, you might need to update the process configuration as described here. For definitions of each test field, see Create a query based on build and test integration fields.

• Customize your work tracking experience
• Upload and download process templates