Kanban Method – feedback loops
Kanban method has seven cadences /feedback loops (written by David Anderson), it is common for new implementations to start with a subset of these. It is also common to repurpose existing meetings. The feedback loop helps to observe our flow and our work on a regular basis, and agree on things we want to do to improve our flow.
| Getting things done | Doing the right things | Doing things better |
| Kanban Meeting | Operations Review | Strategy Review |
| Delivery Planning Meeting | Risk Review | Replenishing |
| Service Delivery Review | ||
The picture referenced from Essential Kanban Condensed Guide by David Anderson and Andy Carmichael
Kanban meeting – A Kanban meeting is similar to the daily standup meeting in Scrum. It is to observe and track the task status and to keep the team on the same page. The difference is that a Kanban meeting is focusing on the flow. The team read from the right of the board to the left, finding the blockage, and ensuring the work moved out of the system.
Replenishment Meeting – A Replenishment Meeting is to pull new items into the queue and prioritize work items. As Kanban is a pull system, the items in the backlog will be pulled and worked on constantly once there is a vacancy in the swimlane. This is to ensure a smooth transition of WIP items
Delivery Planning Meeting – A Delivery Planning Meeting is to review the work done and decide which items to deliver. Issues found in this meeting will be sent to the Risk Review.
Service Delivery Review- The Service Delivery Review is to check whether customer expectations are met in the delivered product. It also looks at the team performance, velocity, and sets metrics.
Operations Review – The Operations Review is to analyze the efficiency of teams and the demand and capacity of each Kanban team. Managers from all departments will share the findings of business performance and initiatives that concern the organization-level changes.
Rish Review – A Rish Review is to look at the issues and bottlenecks identified at the Operations Review and the Service Delivery Review, so the risks will be assesed and the same risks can be avoided in the future.
Strategy Review – A Strategy Review is the top-level meeting to identify potential large-scale problems and find solutions. Decisions made at the meeting will be sent to Operations Review and Service Delivery Review with updated OKRs.
Too many meetings! David Anderson has clearly mentioned he in no way intends to add seven meetings to everyone’s busy work schedules. Since doing the right thing well and finding ways to get better are pretty fundamental to knowledge work, the team can continue existing meetings that serve the above cadences.
