Labeling

The labeling for work scope is important to determine the effectivity of the DevOps team

Based on the reading The Phoenix Project, there are four different types of work that every DevOps unit must identify as they work through the value stream. Identifying this types of work is very important to measure and analyze the effectiveness of the DevOps team in a quarterly manner. This is why correctly labeling tickets and keeping track of them is very important to allocate the limited resources of an organization.

Key Take Aways

  • There are 4 types of work

  • There are two categories of work, Planned and Unplanned.

  • An effective DevOps team should have minimal Unplanned Work, aka Critical Work (CW).

Four (4) Types of IT Work

The first three types of work fall under the category of Planned Work.

The last type of work falls under the category of Unplanned Work, making it the work least desired in any value stream.

DevOps units should avoid running into Unplanned Work as much as they can. In order to do this, they must first keep track of the type of work realized per sprint, therefore, every issue/ticket must always be categorized with one of these labels and in the end of the sprint, every label must be counted to be able to determine the effectivity of the team.

Labels

By the end of each week, we must count the amount of labels to keep track of how the time has been allocated in the team.

In theory, every organization want to allocate the majority of their time and resources in Planned Work and not in Unplanned Work.

Sample of Labels when Ticketing

Last updated