In Azure DevOps, work items are used to track work across the development lifecycle. There are several predefined work item types that you can use based on your process template (Agile, Scrum, CMMI), but you can also customize or create new types. Below are the common work item types categorized by each process:
### 1. **Agile Process Work Item Types**:
- **Epic**: Large body of work that can be broken down into multiple features.
- **Feature**: A significant piece of functionality that can be divided into stories or tasks.
- **User Story**: Describes a piece of functionality from the user's perspective.
- **Task**: A unit of work that contributes to completing a user story or bug.
- **Bug**: Tracks issues that need to be fixed.
- **Issue**: Tracks risks, changes, or impediments.
- **Test Case**: Tracks a single condition or scenario to verify if a feature or system works as expected.
- **Impediment**: Tracks obstacles or blockers affecting progress.
### 2. **Scrum Process Work Item Types**:
- **Epic**: Larger work that is divided into features and product backlog items.
- **Feature**: Represents high-level functionality that delivers business value.
- **Product Backlog Item (PBI)**: Represents a requirement or feature needed by the user (equivalent to a User Story in Agile).
- **Task**: A small unit of work associated with a PBI or bug.
- **Bug**: Tracks issues or defects that need to be resolved.
- **Impediment**: Tracks obstacles that block progress.
- **Test Case**: Describes how a specific scenario should behave, with expected results.
- **Sprint**: Used to plan and track work completed in a sprint.
### 3. **CMMI Process Work Item Types**:
- **Epic**: A large set of requirements or objectives that deliver a significant amount of business value.
- **Feature**: Represents a higher-level functionality that can be split into requirements.
- **Requirement**: Defines a specific feature or function of the application (similar to a User Story in Agile).
- **Task**: A small unit of work that helps fulfill a requirement or resolve a bug.
- **Bug**: Tracks defects in the application.
- **Change Request**: Formal request to change a requirement or work item.
- **Issue**: Represents problems or risks that could affect the success of the project.
- **Review**: Used to track code or document reviews.
- **Risk**: Tracks potential risks that could negatively affect the project outcome.
- **Test Case**: Defines how a requirement or feature should behave under test conditions.
### 4. **Common Work Item Types (Across All Processes)**:
- **Epic**: Large unit of work that can be broken into features or stories.
- **Feature**: Represents a significant piece of functionality.
- **Task**: Tracks a small piece of work required to complete a story or resolve a bug.
- **Bug**: Tracks defects and issues in the product.
- **Test Case**: Defines a condition or scenario to validate features or system behavior.
- **Impediment/Risk/Issue**: Used to track blockers, risks, or issues that could hinder progress.
- **Code Review Request**: Tracks requests for code review, often linked to pull requests.
- **Feedback Request/Response**: Tracks user feedback and its responses.
### Custom Work Item Types:
Azure DevOps allows organizations to define custom work item types according to their unique workflows. You can create new types or modify existing ones using **Azure DevOps Process Customization** tools.
To view the work item types available in your project:
1. Go to **Project Settings** > **Boards** > **Work Item Types**.
2. You’ll see all the predefined work item types for your selected process.
3. Custom work item types can be added here if needed.
### Hierarchical Structure of Work Items:
Work items in Azure DevOps often follow a hierarchy to help organize work:
- **Epics**: Highest level of work, broken into features.
- **Features**: Grouped under epics, broken into stories or PBIs.
- **User Stories / PBIs / Requirements**: Represent individual features or user requirements.
- **Tasks / Bugs**: Small units of work linked to stories, PBIs, or features.
These work item types are foundational for tracking work in Azure DevOps, and selecting the right type depends on your team's process model (Agile, Scrum, CMMI) and project needs.
From Blogger iPhone client