| title | titleSuffix | description | ms.service | ms.topic | ms.author | author | monikerRange | ms.date |
|---|---|---|---|---|---|---|---|---|
Learn key concepts & terms to support Agile tools |
Azure Boards |
Learn about the key terms and concepts to understand the objects and items used to track work in Azure Boards. |
azure-devops-boards |
conceptual |
chcomley |
chcomley |
<= azure-devops |
02/03/2023 |
[!INCLUDE version-lt-eq-azure-devops]
The Microsoft Agile glossary is a short dictionary of terms used in tracking work using Azure Boards. More terms are defined in the following articles:
- Kanban key concepts
- Sprints and Scrum key concepts
- Work item field index
- Project management and navigation glossary
A family of engineering best processes with a goal of enabling rapid delivery of high-quality software and a business approach that aligns development with customer needs and company goals. In this paradigm, frequent inspection and adaptation are necessary, with team work, self-organization, and accountability all critical to project success.
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
Groups one or more work item types to support flexible reporting, queries, and other functions made available through Agile tools. Categories support the process configuration used by the web portal backlog and taskboard pages. For example, you can add custom work item types to the Requirements category and manage them using the product backlog and boards. For more information, see Use categories to group work item types.
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
Fields support tracking a piece of information about the work to perform. Values you assign to a field are stored in the work tracking data store that you can query and generate charts to view status and trends. Your project contains 100 or more data fields. You update data by modifying the data field within a work item. Each work item is associated with a work item type (WIT), and the data you can track corresponds to the fields assigned to the WIT. For a definition of each predefined field, see Work item field index.
[!INCLUDE temp]
Defines a list of menu items or picklist items that are shared across WITs and projects within a project collection. Global lists help to minimize the work that is required to update lists. You can define global lists within WITs that you upload with your process template. Learn more: Manage global lists for work item types. (Only supported for Hosted XML and On-premises XML process models)
Specifies both work item fields and global lists that multiple projects and types of work items can share. Learn more: Manage global workflow (Only supported for On-premises XML process model).
Hidden types categories
Specifies the set of work item types that you don't want users to create manually. By default this set includes:
- Code Review Request and Code Review Response
- Feedback Request and Feedback Response
- Shared Steps and Shared Parameter
- Test Plan and Test Suite
You can use TFS Team Project Manager, an open-source client available from GitHub to quickly determine which WITs belong to the Hidden Types Category.
The Hosted XML process model provides support for customizing work tracking objects and Agile tools for a project by modifying and importing a process template. This process model is only available for select accounts hosted on the Azure Boards cloud platform. For more information, see Hosted process model.
[!INCLUDE temp]
The Inheritance process model provides support for customizing work tracking objects and Agile tools for a project through the user interface. This process model is only available for accounts hosted on the Azure Boards cloud platform. Projects inherit the customizations made to a process. For more information, see Inheritance process model.
Agile process: An issue is a type of work item that defines an item that you want to track as it may impact the completion of other work. It's defined for the Agile process and doesn't appear on any backlog or board. See Manage issues and impediments.
Basic process: An issue is a type of work item that defines some work or code defect that needs to be tracked. It's defined for the Basic process and appears on the product backlog and Issues board.
[!INCLUDE temp] [!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
The On-premises XML process model provides support for customizing work tracking objects and Agile tools for a project. With this model, you can update the XML definition of work item types, the process configuration, categories, and more. You can also update the attributes of fields. This process model is only available for on-premises Azure DevOps. For more information, see On-premises process model.
A picklist specifies an enumerated set of values that appear within a drop-down menu in a work item form. Values also appear in the Value column within the query editor. The method you use to customize a picklist varies. It depends on the field and the process model. For more information, see Customize work.
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
Specifies the default configuration and functional capabilities that your teams can access using the Agile tools. These web portal tools include the product backlog, sprint backlogs, board, and taskboard. (Only supported for Hosted XML and On-premises XML process models)
The work tracking customization method supported by your organization or collection. One of three process models are supported, Inheritance and Hosted XML for Azure Boards and On-premises XML for on-premises Azure DevOps. Learn more: Customize your work tracking experience
Specifies an inter-related set of files that contain the XML definitions for tracking work and defining the initial configuration of other functional areas. The system provides three default process templates—Agile, Scrum, or CMMI. You can create a project and then customize it, or customize a process template that you then use to create a project. (Only supported for Hosted XML and On-premises XML process models)
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
[!INCLUDE temp]
A workflow is an integral aspect of a work item. It's defined by its corresponding work item type. The workflow determines the logical progression and regression of work items. For the Agile process, it tracks the status of work as the work progresses from a New or Active state to a Closed or Completed state. For the Basic process, all work item types use the To Do, Doing, and Done states to track workflow status.
The workflow also specifies the values that appear in the State and Reason drop-down menus. For more information, see Workflow states and state categories.