A workflow represents the sequence of steps or the path that work follows from its initiation to its completion. In Jira, a workflow is composed of a set of statuses and transitions that your issues navigate pass through during the in your defined delivery lifecycle. The workflow is a representation of the process being used by your team or organisation.
Workflow Categories
Workflow categories Workflows play a crucial role in generating the generation of flow metrics. The type of workflow Workflows can be allocated to one of 3 workflow categories and the workflow category utilised by your team directly influences the quantity quality of flow metrics and insights that can be derived from your issue history in Jira. There are The three distinct categories to considerare explained below:
1) Single-Step Workflow
A singleSingle-step workflow Step Workflow consists of one status that encapsulates all work activities related to a work item or issue. A classic in a process. An illustration of this is found in the Jira 's default workflow in Figure 1, which includes the statuses To Do, In Progress, and Done. The To Do status signifies an item that is currently in your backlog, while In Progress indicates that work has commenced on the issue. Finally, Done denotes that the work has been completed.
This is classified as a single-step workflow because all actions pertaining to your issues are represented by a single step: the In Progress status.
2) Multi-Step Workflow
A Multi-Step Workflow is a more structured approach where each the work activity associated with an issue issues is depicted through various steps or statuses within your workflow.
In the Multi-Step example shown on the right, the single In Progress status from the singleSingle-step workflow Step Workflow has been expanded into three distinct work statuses: In Development, In Review, and In QA. This breakdown allows for a more detailed representation of the workflow process.
3) Complete Wait-Step Workflow
A complete workflow Wait-Step Workflow encompasses all the active and waiting phases that your tasks must traverse to reach completion. For instance, in the Complete Wait-Step Workflow example illustrated on the right, the In Review stage from the multiMulti-step workflow Step Workflow has been divided separated into two distinct statuses: Wait Review and In Review.
This thorough The breakdown of all working and waiting statuses enhances the workflow's completeness and facilitates the generation of a comprehensive set of flow metrics, accurately reflecting the true performance of your team's delivery system.
Workflow Category Benefits
The flow data and insights produced generated by Delivery Flow are heavily influenced by the specific category of workflow employed as issues progress through your process. Below is a detailed overview of the benefits associated with each type of workflow.
Benefit | Single-Step | Multi-Step | CompleteWait-Step |
|---|---|---|---|
Work In Progress Metrics |
|
|
|
Average Cycle Time Metrics |
|
|
|
Throughput Metrics |
|
|
|
Issue Type WIP Metrics |
|
|
|
Issue Type Cycle Time Metrics |
|
|
|
Issue Type Throughput Metrics |
|
|
|
Flow Demand |
|
|
|
Time In Status |
|
| |
Work Breakdown Insights |
|
| |
Flow Efficiency |
| ||
Queueing Insights |
|
Utilising Single-Step workflows can yield a wealth of insightful and valuable flow metrics. When you opt for a Multi-Step workflow, you not only gain all the insights provided by a Single-Step workflow but also benefit significantly from the ability to analyze analyse the time spent in each phase work step of your process. This approach allows you to deconstruct your process, enabling a clearer understanding of where time is being spent. This analysis can be conducted at both the system level and the individual issue level.
While both Single-Step and Multi-Step workflows offer significant benefits, we strongly encourage you to transition your process definitions to Complete Wait-Step workflows. The benefits of this shift can be transformative. Complete Wait-Step workflows enable the production of Flow Efficiency metrics and insights into the level of queuing within your delivery system. These metrics are essential for identifying waste, bottlenecks, and inefficiencies in your processes, allowing you to fully comprehend the impact of excessive dependencies and demands on your teams.
Start where you are by using your existing workflow, then evolve towards a Complete Wait-Step Workflow.
If you are currently utilising a Single-Step or Multi-Step workflow in your project, then this is where you should start. Begin by creating Workflow Maps based on your existing workflows to generate flow metrics for your work. However, to develop a deeper understand of the inherent challenges within your Delivery System, we cannot emphasise enough the importance and value of Complete Wait-Step workflows.
Related:
For more information on Flow Efficiency, read Flow Efficiency – The Most Important Metric When Developing Software?.
If you are thinking about evolving to Complete Wait-Step Workflows, read Amending Jira Workflows to Improve Flow Metrics.
If you use Single-Step or Multi-Step workflows, read Using Jira Cycle Time to Improve Delivery.
Next:
Cards extension