8.2.1.1 Kanban Workflows*
For more information, see section 3.5.1.
8.2.1.2 Kanban Backlog*
For more information, see section 3.5.2.
8.2.1.3 Performance Data
Performance data, such as cycle time, lead time, and throughput, can be used to assess the team's overall performance. By tracking these metrics over time, the team can identify trends and measure the impact of changes to the workflow.
For more information, see sections from 4.2 to 4.16.
8.2.1.4 Team Feedback
In Kanban, retrospectives focus on continuous improvement by using real-time data and team feedback to refine workflows. Kanban does not mandate scheduled retrospectives, but teams often hold them periodically or when performance issues arise.
Team feedback enhances retrospectives by facilitating:
- Flow-Based Reflection: Feedback revolves around improving efficiency, reducing bottlenecks, and optimizing work-in-progress (WIP) limits.
- Data-Driven Discussions: Teams analyze cycle time, lead time, and throughput metrics to support feedback with evidence.
- Work Visualization: The Kanban Board serves as a shared reference, helping the team identify problem areas.
- Feedback Loops: Regular feedback from team members ensures process adjustments align with real challenges.
- Psychological Safety: Encouraging open discussions fosters a culture of trust and improvement.
By integrating team feedback into retrospectives, Kanban Teams maintain agility and drive continuous, data-informed improvements.
8.2.1.5 Key Performance Indicators (KPIs)
KPIs can be used to measure the team's performance against specific goals. By tracking KPIs, the team can identify areas where they are excelling and areas where improvement is needed.
For more information, see section 6.3.3.3.
8.2.1.6 Cycle and Lead Times
Cycle time and lead time are two important metrics used to assess the efficiency of the Kanban process. By analyzing these metrics, the team can identify bottlenecks and take steps to improve the flow of work.
For more information, see sections 4.5 and 4.6.