Process radiators to aid efficiency via components in JIRA
Should your company be running an ISO 9001:2015 process quality program, you will come across the need for activity level process radiators embedded in the task allocation and tracking system.
For the JIRA system, components feature can really come in handy for activity classification based on which process the activity belongs. Embedding this in the task allocation and tracking system further helps ensuring stakeholders view Just-In-Time data against each process for timely process engineering.
We could also refer to it as goal specific grouping of activities.
Following lists the advantages of using processes components for each unit scaled across the organization.
Component Filters can be integrated with confluence for automated updates of process level status reports.
Easy data collection to measure and control adherence to process quality.
Filters can be created on the Kanban board for each component to identify process level activity in a mutually exclusive board.
Activities done on regular basis in any functional unit can form regular activities against a baselined process or can be to improve on a process. JIRA tickets for process improvements can have corresponding process component that it wants to improve and a global process component (could be termed "Process Improvement" consistent across the board).
Filter "Process improvement" on Kanban board can easily identify all improvements done in the quality management system for the complete unit demonstrating adaptation and emergence. [Assuming each unit has a separate JIRA project for its operations and programs management]
Global process level dashboards can be created with JIRA gadgets to determine efficiency and effectiveness for the unit. JIRA gadgets can easily allow for process quantification and trend capture for metrics demonstrating/justifying if process objectives are being met or not.
Monthly or quarterly reviews of the filter Kanban can help identify focused/neglected areas i.e. measure process dynamicity and how active it is.
JIRA allows each component to have a component owner i.e. process owner.
Any activity with selected process component auto assigns to the process owner for decentralized process management and process co-ownership in a unit. For large teams this can be extended against roles and responsibilities for noise free scalability in the same project workspace.
It’s easy to identify activities that do not fall into any process needing intervention to create a new process/sub-process or extend the scope of a process.
Processes generally feed into each other forming a connected system, it’s easy to view and manage process linkages.
In case a process has one or more sub-processes, this can be managed with ticket nesting forming parent-child relationships and with selected components allowing for two-dimensional process management.
This process architecture can be easy scaled across each function for process management consistency and allow for creation of company-wide dashboards to demonstrate leadership and team commitment to continual service improvement in the quality management system.
The process boards and filters can easily support the needs for Must Have clauses landing in Check and Act stages of ISO 9001:2015.
To summarize the benefits, organizational and unit transparency, just-in-time updates and efficient process engineering, process co-ownership with scalability.