Curriculum
In this tutorial, you’ll learn about various Work Items that are used in Azure DevOps Boards and when to use them.
| Work Item | Description | When to use |
|---|---|---|
| User Story | A high-level description of a feature that provides value to the end-user. | When capturing requirements from stakeholders or when planning a sprint backlog. |
| Task | A piece of work that is needed to complete a user story or bug. | When breaking down a user story or bug into smaller, manageable pieces of work. |
| Bug | An issue or problem that needs to be fixed. | When tracking defects or issues found during testing. |
| Epic | A large body of work that cannot be completed in a single sprint. | When tracking work that spans multiple sprints or releases. |
| Issue | A problem or concern that needs to be addressed. | When tracking non-technical issues or concerns, such as legal or compliance issues. |
| Test Case | A set of steps that need to be followed to test a specific feature or functionality. | When creating test plans for a project or when planning test cases for a sprint. |
| Test Suite | A collection of test cases that are grouped together for testing purposes. | When grouping related test cases together for efficient testing. |
| Feedback Request | A request for feedback from stakeholders or end-users. | When seeking feedback on a new feature or functionality before it is released. |
| Impediment | A problem or issue that is preventing the team from making progress. | When tracking obstacles or issues that are impacting the team’s productivity. |
| Risk | A potential problem or issue that may impact the project in the future. | When identifying and tracking potential risks to the project. |
By understanding the different types of work items available in Azure DevOps and when to use each one, teams can effectively track and manage their work throughout the software development lifecycle.