A kanban meeting agenda is a short, structured list of items for a daily or weekly team sync, focused on moving work through the kanban board. The core agenda is: review the board, discuss blockers, and plan the next work items.
What Is a Kanban Meeting?
A kanban meeting—often called a daily standup, daily huddle, or flow meeting—is a recurring team gathering where members review the kanban board and coordinate work. Unlike a traditional status meeting, the focus is on the flow of work, not on individual progress reports. The meeting is typically time-boxed to 15 minutes for daily standups or 30–60 minutes for weekly planning sessions.
The kanban board itself is the central artifact. Each column represents a stage in the workflow (e.g., To Do, In Progress, Done), and cards represent work items. The meeting is organized around the board, not around a slide deck or a list of individual updates.
Why Have a Kanban Meeting?
The purpose of the kanban meeting is to identify bottlenecks, unblock team members, and make sure work is flowing smoothly. It is not a reporting session. The team looks at the board and asks questions like:
- Is any card stuck in a column for too long?
- Are there too many items in progress (exceeding the work-in-progress limit)?
- Does anyone need help to complete a task?
- What is the next most important item to pull into the next column?
By keeping the meeting short and board-focused, the team can quickly coordinate and return to work. The meeting also helps surface process issues early, such as a column that is always overloaded or a dependency that is not visible on the board.
How to Structure a Kanban Meeting Agenda
A typical kanban meeting agenda has five parts, each with a clear timebox. The facilitator (often the team lead or a rotating facilitator) walks through the board and guides the discussion.
- Check the board (2–3 minutes): Everyone looks at the board. The facilitator reads out the columns and the cards in each one. This is a quick visual scan, not a detailed update.
- Identify blockers (3–5 minutes): The team asks if any card is blocked. A blocked card is one that cannot move forward because of a dependency, missing information, or an external issue. The team discusses how to remove the blocker.
- Review work-in-progress (WIP) limits (2 minutes): If a column has more cards than the WIP limit allows, the team decides which cards to finish first or which to move back. This is a key kanban practice to prevent overloading.
- Plan the next items (3–5 minutes): The team decides which card(s) to pull into the next column next. This is based on priority and capacity, not on who is free.
- Confirm actions (1–2 minutes): The facilitator summarizes any actions, who is responsible, and when they will be done. This is usually just a quick recap.
For a weekly kanban meeting, the agenda can be expanded to include a review of cycle time (how long cards take to go from start to done), a review of the board’s layout, and a discussion of process improvements.
Common Mistakes in Kanban Meetings
Even with a clear agenda, kanban meetings can go off track. Here are common pitfalls and how to avoid them:
- Turning it into a status report: If each person goes around the room giving a personal update, the meeting becomes a status report, not a flow review. Keep the focus on the board and the work items.
- Going too deep into problem-solving: The meeting is for identifying blockers, not solving them. If a blocker requires a long discussion, schedule a separate meeting with the relevant people.
- Ignoring WIP limits: If the team does not respect WIP limits, the board will be overloaded and the meeting will be chaotic. Enforce the limits or the meeting loses its purpose.
- Meeting too long: A daily meeting should be 15 minutes. If it regularly runs longer, the team is probably discussing details that belong elsewhere.
- Not having a facilitator: Without a facilitator, the meeting can drift. Rotate the role so everyone shares responsibility.
Kanban Meeting Agenda Template
Below is a blank template you can use for your own kanban meeting. Fill in the date and the items for each section. Keep it on a single page.
| Date | Facilitator | Timebox |
|---|---|---|
| __________ | __________ | 15 min |
1. Board Review (2–3 min)
List any cards that are stuck or not moving:
• _______________________________
• _______________________________
2. Blockers (3–5 min)
List any blockers and who is responsible for resolving them:
• Blocked card: _______________ / Owner: _______________
• Blocked card: _______________ / Owner: _______________
3. WIP Limit Check (2 min)
Any column over its WIP limit? Which card will be finished first?
• Column: _______________ / Card to finish: _______________
4. Next Items to Pull (3–5 min)
Which cards will be pulled into the next column?
• Card: _______________ / Into column: _______________
• Card: _______________ / Into column: _______________
5. Action Items
• _______________________________
• _______________________________
Sample (fictional): Date: 2025-03-14, Facilitator: Alex. Blockers: “Update login page” blocked by missing design – owner: Sam. WIP check: “In Progress” has 5 cards (limit 3) – finish “Fix checkout bug” first. Next pull: “Write API docs” into Review. Action: Sam to get design by 3 PM.
Choosing the Right Meeting Cadence
Not every team needs a daily kanban meeting. The cadence should match the team’s need for coordination. A daily meeting is useful when there are many handoffs or dependencies. A weekly meeting may be enough for a stable team with few external dependencies. Consider these factors:
- Team size: Larger teams may need more frequent check-ins to stay aligned.
- Work complexity: Complex tasks with many dependencies benefit from daily coordination.
- Stability: If the board rarely changes, a weekly review may suffice.
- Remote vs. co-located: Remote teams often need a daily sync to replace informal hallway conversations.
You can also adjust the agenda length. A 10-minute daily standup might only cover blockers and next items, while a 30-minute weekly meeting can include process metrics and improvement ideas.
Frequently Asked Questions
What is the difference between a kanban meeting and a scrum standup?
A scrum standup is part of the Scrum framework and focuses on what each person did yesterday, will do today, and what is blocking them. A kanban meeting focuses on the flow of work on the board, not on individual roles. In kanban, the team looks at the board and asks what needs to move next, rather than having each person report.
Who should attend the kanban meeting?
Anyone who works on the kanban board should attend. This includes developers, designers, testers, and any other roles that handle cards. Stakeholders who do not directly work on the board may attend occasionally, but they should not dominate the meeting. The meeting is for the team to coordinate, not for status reporting to managers.
How do you handle a blocked card in a kanban meeting?
When a card is blocked, the team first identifies the cause. If the blocker can be removed quickly (e.g., a missing approval), the team assigns someone to resolve it. If the blocker is external (e.g., waiting for a vendor), the team may decide to move the card back to a previous column or mark it as blocked on the board. The key is to make the blocker visible and assign an owner.
What if the meeting runs over the timebox?
If the meeting regularly runs over, the facilitator should cut off deep discussions and schedule a separate meeting for those topics. The kanban meeting is for identifying issues, not solving them. If the team keeps going over, reduce the agenda to just blockers and next items, or increase the timebox if the team genuinely needs more time.
Can a kanban meeting be done asynchronously?
Yes, some teams use a digital kanban board and post updates asynchronously, especially when team members are in different time zones. The team can comment on cards and use a shared document for the agenda. However, a live meeting is better for real-time problem-solving and team cohesion. If you go asynchronous, make sure the board is kept up to date and someone reviews it daily.