Kanban 102 (A Case Study) – A Scrum Team’s Journey into the World of Scrumban

Most everyone has heard of Kanban, Work in Progress, Continuous Flow, etc.

This presentation will go beyond the basics (101) telling the story of a Scrum Team’s evolution to Scrumban. This presentation will discuss the underlying reasons the team went to Kanban, what was experienced at first, and what adjustments were made to make Kanban successful in their environment.

The objective of the presentation is not to give a one-size-fits-all answer, but rather a compelling exploration into the world of Kanban.

Topics to be discussed:

• Case Study – our project
• Waterfall to Scrum
• Shortcomings of Scrum in a rapidly changing environment
o Time box and scope box
o Issues with estimating
o Meaningful metrics
• Evolution to Scrumban
o Implementing Kanban while maintaining Scum team dynamics
o How we maintained the priority list (creating the “batting order”)
o Why we went to WIP limit of “1”
o Estimating and Sizing for Continuous Flow Metrics (Throughput)
• Kanban Value Team Side
o Backlog grooming in a Kanban environment
 The role of estimation in a continuous flow environment
o Keeping true to roadmap/big picture in a rapidly changing environment
o Helping stakeholders understand impact of hyper-change
• Kanban Delivery Team Side
o How to be true to Agile Manifesto values and principles w/o scum boxes (time and scope)
o When to do planning, release, and retro outside of Sprints
o Keeping it together in a dispersed team (including a discussion on tools)
o How to deal with stalled/blocked items
• Other
o WIP limit – Little’s Law
o Wrong reasons to go to Kanban
 Won’t fix Scum dysfunctions/anti-patterns
o Personal Kanban – the Trello phenomenon
 “Get It Done”