
Member-only story
Azure DevOps work items explained
For beginners in the Agile world, Azure DevOps Work items might sound a little confusing. This article will explain what they are and their differences.
The work items represent the core of the Azure DevOps tracking system and can be a bug, a requirement, a general to-do, and so on.
Each work item has a unique ID to keep track of its references from its creation to its implementation as a piece of executable software.
There are several types of working item:
- Epic (Basic, Agile, Scrum, and CMMI)
- Feature (Agile, Scrum, and CMMI)
- User Story (Agile), Product backlog item (Scrum), Requirement (CMMI)
- Task (Basic, Agile, Scrum, and CMMI)
- Impediment (Scrum), Issue (Agile and Basic)
- Bug (Agile, Scrum, and CMMI)
While epics and features reflect the business focus, user stories and tasks are related to the development.
