Single Company Project
If your organization follows a single standardized process and Jira workflow, it is essential to establish a one-to-one mapping for Delivery Flow. In the illustrative example depicted in figure 1 below, four Flow Lanes have been established, with each Jira status being mapped to its corresponding lane. Additionally, detailed information regarding work, start, and end lane specifications has been defined in the flow map.
Multiple Company Projects
If your organization manages multiple company projects and workflows, strategic decisions are required. When multiple workflows correspond to the same process, as illustrated in Table 1 below, establishing a many-to-one mapping is advisable.
Jira Workflow One | Jira Workflow Two |
|---|---|
Backlog | To Do |
Ready for Dev | Selected for Development |
In Progress | In Progress |
Done | Done |
Table 1. Comparison of two distinct Jira workflows representing identical processes
Despite variations in status labels, both workflows symbolize the same processes. Delivery Flow has the capability to generate a unified map for tracking flow metrics across these projects (refer to Figure 2).
Conversely, in cases where workflows across company projects exhibit significant differences, it is recommended to create a one-to-one mapping for each project, similar to the illustration in Figure 1 above.
Next:
Cards extension