Any phase · Ways of working
Decide what comes next in a Kanban team
In Kanban, work flows continuously. A regular replenishment meeting decides what enters the board next, so the team always works on the most valuable items.
About 30-60 minutesEvergreenLast reviewed 5 November 2026
Who this applies to
- Skills it builds
- Delivery and executionPrioritisation and roadmapping
- PM types
- All
- Product types
- All
- Starting points
- All
- Ways of working
- Kanban
- Experience
- All
- Size of organisation
- All
Steps, by experience
Beginner (under 1 year)
- Hold a short meeting weekly or when the 'ready' column runs low.
- Review the options and the latest priorities.
- Choose the next items and check they are clear enough to start.
- Respect work-in-progress limits; do not overload the board.
- Tell stakeholders what was chosen and what was not.
Intermediate (1 to 4 years)
- Hold regular replenishment with clear criteria.
- Respect work-in-progress limits.
- Use cycle time to set expectations.
Experienced (5+ years)
- Use classes of service for urgent and fixed-date work.
- Forecast with throughput data.
- Balance new features, fixes and technical health.
Who can do this
Owner: Product manager
Can be delegated to
- Delivery Manager or Scrum Master: Facilitate and track flow metrics
- Product Owner: Prepare options
Reviewed by: Delivery Manager
Tool examples
- Jira
- Use a Kanban board with column limits.
- Trello
- Use a 'ready' list with a card limit.
- Linear
- Use triage to choose what enters the backlog.
Definition of done
- Regular replenishment in place
- Work-in-progress limits respected
- Choices shared with stakeholders
Common pitfalls
- Adding work whenever someone asks
- Ignoring work-in-progress limits
- No visible priorities