First meeting of each 2 week cadence, the Kanban version of Sprint Planning meeting. Or whenever the work in “Selected for Development” column runs out.
To keep a steady stream of tasks moving across the Kanban board, the number of tasks in the backlog must be selected and this takes place during the Replenishment Meeting.
At the end of the meeting all of the development team should have enough detail on each story and asked enough questions to be able to start work on the stories without another meeting.
Key things to keep in mind during Replenishment meetings are the Prioritizing Work Efficiently: Classes of Service in Kanban | Nave of new work items, forecasting Fixed Delivery Dates items, larger strategic objectives, and whether any tasks need specific team member skills to be completed. The Replenishment meeting should involve portfolio/product owners and product development management.
Attendees
PO and Dev Team mandatory, stakeholders optional.
Duration
1 hour if backlog refinement done, up to 4 hours if no backlog refinement prior.
Agenda
- Identify the high level goals – 5 mins
- Select the next Story/Bug from the top of backlog
- Describe the story and the problem to solve – PM, CEO, CTO etc – 5 mins
- Ask questions to identify In Scope, Out of Scope, Scenarios/ACs – 5 mins
- Split out Tasks to complete – 5 mins
- Estimate Story/Bug (not sub-tasks) – 2 mins
- Repeat until there is 2 weeks worth of work in Selected for Dev that has all the details ready to start work on