Maps for Company Projects
Single Company Project
If your organisation follows a single standardised 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, five Flow Lanes have been established, with each Jira status being mapped to its corresponding lane. Detailed information regarding work, start, and end lane specifications has been defined in the flow map. Additionally, the map also contains a default query that will be recommended to team members when they use the map to generate flow metrics.
This workflow map was created using the “Project-based” map option. Project-based maps only use statuses the project utilises.
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 possible.
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). This workflow map was created using the “Custom multi-project” map option. This option creates a very basic initial map, but all valid statuses within Jira are available for use.
In cases where workflows across company projects exhibit significant differences, it is recommended to create a one-to-one (Project-based) mapping for each project, similar to the illustration in Figure 1 above.
Next:
