Presentation on theme: "Tech Next - Scrum Vs Kanban practiced in product development Tech Next, May 7, 2011"— Presentation transcript:
Tech Next - Scrum Vs Kanban practiced in product development Tech Next, May 7, 2011
Tech Next - Some issues with scrum Estimates decide what gets taken up in a sprint. Estimates are not always accurate. –Underestimation leads to idle capacity –Overestimation leads to overwork and burnout. Some urgent work or bright ideas do arise in the middle of a sprint. Support and maintenance teams find it tough to work in iterations. All work may not be based on user stories. E.g. hiring, IT setup, training etc. You do require roles other than the 3 prescribed by scrum. E.g. IT engineer, trainer, recruiter etc.
Tech Next - What is Kanban More a tool than a process E.g.Japanese royal garden in Tokyo Applicable wherever there is flow Each column represents a step Each step has a prescribed kanban limit.
Tech Next - Advantages of Kanban Flexible – easy to adopt –No timeboxed iterations –More than 3 roles possible –Work not limited to user stories –Estimation/ daily standups not mandatory Visibility into bottlenecks and capacity Can use scrum practices wherever needed
Tech Next What is not a requirement for Kanban? A. Flow of work B. Steps C. Daily standups D. Capacity limits for steps 2. Which one of the following is a good reason to use kanban? A. Estimates become more accurate B. Visibility into bottlenecks and capacities C. Teams can put away new work in the product backlog D. No planning required Quiz
Tech Next - Differences- scrum & Kanban Scrum has fixed roles. Kanban doesnt Scrum prescribes estimation using planning poker – Kanban doesnt. Scrum has relative sizing of stories – Kanban believes in breaking down to tasks that are of similar size. Kanban limits the capacity at each step – scrum limits capacity per iteration. Scrum prescribes timeboxed iterations – it resists changes within an iteration.
Tech Next - Similarities- scrum & Kanban Both work well with cross functional teams Both are based on individuals pulling work than work being pushed on them. Both are empirical and flexible. You are supposed to experiment with the process and customize it to suit your project. Both allow working on multiple products simultaneously. Both are lean and agile
Tech Next - Kanban – a case study Hiring process flow has following steps –Shortlist resumes –Phone screen –Technical test –Technical round –HR round –Final offer –Offer Accepted/ Rejected Cross functional team- HR, Project Managers, QA, PR, Event Managers etc.
Tech Next - Kanban Board for hiring
Tech Next - Kanban- case study (contd) Each step is owned by one or two individuals. One column on Kanban board for one individual. Number of items on an individuals plate are placed above the horizontal line. Bottlenecks are clearly visible. We kept the limit of 3 for all individuals for now. But the capacity was never used due to upstream bottleneck at the scheduling step