Cadences of Kanban are meetings that allow a team to deliver working software at a stable and steady pace. A team that can deliver at a regular cadence can manage its velocity. 

The term "delivery cadence"...implies establishing a pattern of delivery of working software at a regular interval. Unlike Agile development methods which have time-boxed iterations, Kanban cadences allow it to adjust to its own natural pace.  The seven Kanban cadences are

• Kanban Meeting
• Replenishment Meeting
• Operations Review
• Delivery Planning Meeting
• Service Delivery Review
• Risk Review
• Strategy Review

The seven Kanban cadences can be grouped into three groups if we look at their functions:

• Getting things done: Kanban Meeting, and Delivery Planning Meeting;
• Doing the right things: Operations Review, Risk Review, and Service Delivery Review;
• Doing things better: Strategy Review, and Replenishen Meeting.

They can also be grouped into two groups in terms of the purpose of the meeting:

• service delivery: Kanban Meeting, Replenishment Meeting, and Delivery Planning;
• improvement/evolution: Service Delivery Review, Operations Review, Risk Review, and Strategy Review.

Image Source:   Essential Kanban Condensed Guide by David Anderson and Andy Carmichael

As you can see in the image above, two flows connecting the seven cadences of Kanban. One is the flow of information, which delivers the feedback from one cadence to another. The other one is the flow of change, which is about the actions and decisions made in one cadence and then have an impact on that made in another cadence. 

What Kaban cadences are

• Kanban Meeting

Frequency: daily

Duration: 15 minutes

Attendee: the service delivery manager, the team

A Kanban meeting, aka daily 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

Frequency: weekly or on-demand

Duration: 20-30 minutes

Attendee: the product owner, the development management, the team

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

Frequency: per delivery

Duration: 1-2 hours

Attendee: the service delivery manager, the team

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

Frequency: bi-weekly

Duration: 30 minutes

Attendee: the  service delivery manager, the team

The Service Delivery Meeting 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

Frequency: monthly

Duration: 2 hours

Attendee: the  service delivery managers, the service request managers, customer representatives, other managerial

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.

• Risk Review

Frequency: monthly

Duration: 1-2 hours

Attendee: the  service delivery managers, the team, other managers

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

Frequency: quarterly

Duration: half-day

Attendee: senior executives, Product Owners, customer-facing seniors

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.

Conclusion

Kanban cadences are meetings in a regular rhythm. It is an important feature of Kaban meetings and works as the heartbeat of the delivery process. Kanban cadences facilitate the continuous information flow within the organization, so the team can check the process and feedback, continuously improve itself and deliver working software.  

Reference

1.  Kanban: Stop Starting, Start Finishing, https://www.zentao.pm/blog/the-abcs-of-kanban-method-436.html

2.  6 Kanban Practices, https://www.zentao.pm/blog/6-kanban-practice-438.html

3.  Kanban and Kanban tools, https://www.zentao.pm/article/kanban-agile-tool-free-and-open-source-229.html

4. David J Anderson.  K a n b a n: Successful Evolutionary Change for Your Technology Business. 2010

5.  Improve Your Information Flow with Kanban Cadences, https://kanbanzone.com/2019/improve-your-information-flow-with-kanban-cadences/