Microsoft Azure DevOps – Boards – Work Items

Hi All,

LIFE IS BEAUTIFUL 🙂 I hope we all are safe 🙂 STAY SAFE, STAY HEALTHY, STAY HOME 🙂

Background: We have started discussing Azure DevOps. In last 12 articles of Azure DevOps we discussed

  1. Introductory part of Azure DevOps – Introduction of Azure DevOps
  2. Organizations in Azure DevOps – What are Azure DevOps Organizations, how to create Organizations, permissions etc.
  3. Microsoft Azure DevOps – Deleting and Recovering Organization
  4. Microsoft Azure DevOps – Projects – What are Azure DevOps Projects, how to create Projects, permissions etc.
  5. Microsoft Azure DevOps – Types of Projects – Public project, Private project
  6. Microsoft Azure DevOps – Project settings
  7. Microsoft Azure DevOps – Deleting and Recovering Projects
  8. Azure DevOps – REST APIs – Part 1 – for Projects
  9. Azure DevOps – REST APIs – Part 2 – Creating Personal Access Tokens (PATs)
  10. Microsoft Azure DevOps – REST APIs – Part 3 – Personal Access Tokens (PATs) – “Revoke”, “Edit” and “Regenerate” operations
  11. Microsoft Azure DevOps – Boards
  12. Microsoft Azure DevOps – Create a Wiki for your project

In this article we will move ahead and will discuss work item types in Azure DevOps

Take away from this article: At the end of this article we will got to know about

  1. Selecting process while creating the new Project in DevOps
  2. What are work items
  3. Different type of work items in different DevOps processes
  4. Rest call to get all work items for my project

My main motto to write on work items to explain in details the DevOps processes. I’ll start writing on DevOps processes from next article. Azure DevOps provides us 4 default processes but we will discuss those in next article 🙂

Work Items :

  1. With the help of Work Items we track our work. For example Features, User Stories, Tasks, Bugs
  2. There are different type of Work items to track different type of information
  3. Work item is a database record that contains the definition, assignment, priority, and state of work
  4. Work items are used to share information, assign work to team members, track dependencies, organize work.
  5. Every work item is assigned an identified which is unique within an organization or project collection
  6. Work items can be linked to each other to support tracking dependencies, roll up to work, and reports
  7. What type of work items (OR which work items) are available to my project is based on the process which I selected while created the project as shown in below Fig
Microsoft Azure DevOps – Boards - Work Items Creating a new project - selecting Work Item process
Fig : Microsoft Azure DevOps – Boards – Work Items – Creating a new project – selecting Work Item process

Following are the mostly common used Work item types:

Epic:

  1. This work item type is available in all default processes – Basic, Agile, Scrum and CMMI ( Capability Maturity Model Integration)
  2. Are used to group work under larger scenarios
  3. Epic represents business initiative
  4. Examples
    • Increase customer engagement
    • Improve performance
    • Support mobile application
    • Implement Azure DevOps

Feature:

  1. This work item type is available in Agile, Scrum and CMMI processes
  2. Are used to group work under larger scenarios
  3. One complete feature of Software
  4. Examples:
    • Add mobile shopping cart to application / project
    • New look and feel to application / project

User Stories:

  1. This work item type is available in Agile process
  2. In agile process, By creating backlog of user stories we create project plan
  3. User stories represents the work we need to develop and ship
  4. User stories define the applications, requirements, and elements that team needs to create
  5. Product owner defines user stories and can priorities by using “State Rank field”
  6. Team then estimate the work effort
  7. Team then in sprint divide user stories into the tasks

Product backlog item:

  1. This work item type is available in Scrum process
  2. Similar to User Stories in Agile process
  3. To plan software / application using Scrum product backlog work item type is used
  4. Product owner defines product backlog item
  5. Product backlog items highlights what value customer will receive rather tasks need to be implemented by development team
  6. Product owner priorities the product backlog items using “priority” and “Business Value” field
  7. Business Value field in Product Backlog Items – This number specifies the relative value of Product backlog Item as compared to other Product Backlog Item. The higher the number, the greater business value

Requirement :

  1. This work item type is available in CMMI process
  2. This work item types are used to track the work
  3. Team plans project in CMMI process with the help of Features and Requirements
  4. In CMMI process for one feature there will multiple requirements
  5. Program manager links Requirements to Features
  6. When sprint starts, Tasks are created for requirements

Impediment 

  1. This work item type is available in Scrum process
  2. Impediments work items are used to track events that may block progress or ship a Product backlog item in Scrum process

Task:

  1. This work item type is available in Basic, Agile, Scrum and CMMI processes
  2. Are used to track the work
  3. In Scrum,
    • Task can be defined at start of every sprint.
    • Task can include development, testing etc.
    • Task can be defined to implement Product Backlog Items

Bug:

  1. This work item type is available in Agile, Scrum and CMMI process model
  2. Tracks code defects

Issue:

  • This work item type is available in Basic and Agile process
  • Used to track work
  • In Agile Process – Defines an work item that defines an item that we want to track as it may impact the completion of other work. OR to track events that may block progress or shipping a user story.
  • In Basic Process – Tracks code defects

Test Case

  1. This work item type is available in Basic, Scrum, Agile, CMMI process
  2. Test manager creates test cases and links to either Product Backlog Item or Bugs in scrum process
Microsoft Azure DevOps – Boards - Work Items - Work Item types in Basic process
Fig : Microsoft Azure DevOps – Boards – Work Items – Work Item types in Basic process
 Microsoft Azure DevOps – Boards - Work Items - Work Item types in Agile process
Fig : Microsoft Azure DevOps – Boards – Work Items – Work Item types in Agile process
Microsoft Azure DevOps – Boards - Work Items - Work Item types in Scrum process


Fig : Microsoft Azure DevOps – Boards – Work Items – Work Item types in Scrum process
Microsoft Azure DevOps – Boards - Work Items - Work Item types in CMMI process
Fig : Microsoft Azure DevOps – Boards – Work Items – Work Item types in CMMI process

Get all the work item types for my project:

GET https://dev.azure.com/{organization}/{project}/_apis/wit/workitemtypes?api-version=6.0

Example:

Microsoft Azure DevOps – Boards - Work Items - Getting list of all work items for the given project
Fig : Microsoft Azure DevOps – Boards – Work Items – Getting list of all work items for the given project

References:

  1. Work Item Types – List (Azure DevOps Work Item Tracking) | Microsoft Docs
  2. Define features and epics, organize backlog items – Azure Boards | Microsoft Docs

Thanks for reading 🙂 Feel free to discuss / comment / questions 🙂 SHARING IS CARING 🙂

Share In Teams:

Enjoy the beautiful life 🙂 Have a FUN 🙂 HAVE A SAFE LIFE 🙂 TAKE CARE 🙂

One thought on “Microsoft Azure DevOps – Boards – Work Items

This site uses Akismet to reduce spam. Learn how your comment data is processed.