Azure Devops – Features, Epics, User Stories and Tasks
High Level and Lower Level Components in Agile (azure devops)
Epics and Features are higher level containers. User Stories and Tasks are more sub-level components.
- Epics can DIRECTLY be broken into User Stories/Tasks (aka backlog items)
- Epics IDEALLY need to be broken down into Features.
- Features can be broken down into User Stories / Tasks / Backlog Items. These tasks / stories are what fit into SPRINTS.
How to add a task to an Epic?
From Epic –> Add Link (Task or User Story). Fill in the details.
Where does a backlog item fit in?
Typically, a backlog item is a task that belongs to a Feature (or directly to an Epic).
Anuj holds professional certifications in Google Cloud, AWS as well as certifications in Docker and App Performance Tools such as New Relic. He specializes in Cloud Security, Data Encryption and Container Technologies.
Anuj Varma – who has written 1210 posts on Anuj Varma, Hands-On Technology Architect, Clean Air Activist.
Are features usually shared across tickets spanning over multiple iterations?