7.2.1.1 Existing Kanban Metrics*
Existing Kanban metrics, such as lead time, cycle time, and work-in-progress (WIP) limits, provide a baseline for measuring performance. By tracking these metrics over time, teams can identify trends and patterns, enabling data-driven decisions to improve workflows.
For more information, see sections 4.2 to 4.16.
7.2.1.2 Existing Kanban Workflows*
For more information, see section 3.5.1.
7.2.1.3 Existing Kanban Backlog*
For more information, see section 3.5.2
7.2.1.4 Existing Kanban Reports
Existing Kanban reports provide a structured way to visualize and analyze Kanban metrics, offering a comprehensive overview of the team's performance. These reports can include visualizations of key metrics, trend analyses, and comparisons to historical data. By reviewing and analyzing these reports, teams can identify opportunities for improvement and take action to address them.
For more information, see sections 4.2 to 4.16.
7.2.1.5 Existing Forms and Templates
Existing forms, such as bug reports or incident reports, can be used to document issues and blockers. These forms help capture important information, such as the nature of the issue, its impact, and any potential solutions. Forms enable users and team members to collaborate across workflows, workspaces, and organizations. They can be created at the board level and made accessible to users. Once a form is submitted, a relevant task is automatically created at the board level. Teams can then pick up the task, work on it, and, once completed, notify the user of the result. Automation can be implemented to further streamline form processing. Existing templates, such as standard operating procedures or troubleshooting guides, can be used to address common issues and blockers. These templates help streamline the issue resolution process and reduce the time required to complete tasks.
For more information, see section 5.4.