3. ScrumBan is
● Combination
● Application of Kanban method with scrum support.
● Applying Kanban together with Scrum concepts.
● Highly influenced by Kanban Model of Work.
So.... Need to understand Scrum & Kanban for
understanding ScrumBan
3
4. When to Use Scrumban
● Uncertainty
● Production Support/ Maintenance
● Helpdesk Support
● Projects with frequent requirement changes
● Work like System integration packaging or
Deployment.
Those who want to practise Agile & Lean :)4
9. Kanban - History
● In 1940s, Toyota Production System under the
leadership of Taichii Ohno came up with better
engineering process for “Just In Time” delivery process
called “KANBAN”
● KANBAN is a Japanese term meaning visual signal
or card. Toyota engineers use the same for actual
manufacturing work. Image Source : en.wikipedia.org/wiki/Taiichi_Ohno
9
10. Kanban journey to Software World
● A community was formed around 2007
with David J Anderson and few others
as main stakeholders.
● Kanban today has its own success story
to share in software world.
Image Source : David J Anderson Twitter Handle
10
11. Why Visual Signal is important?
● Human brain processes visual information
almost 60,000 times faster than textual
information
● Almost 40% of all nerve fibers connected to
brain linked to retina
11
12. 3 Core Properties of KANBAN
1. Visualize the workflow
2. Limit Work in Progress
3. Measure & Manage Work Flow ( Lead time /
Cycle Time)
12
13. 1. Visualize the workflow
● Make the Work & its flow
Visible
● How: Split in such a way so
that it can be written on a
postcard size paper
13
16. 2. Limit Work In Progress (WIP)
● Each column in kanban represents
WorkFlow State.
● Each workflow state is assigned an explicit
limit
○ This limit is deduced by historical data / Availability
basis - Improve Transparency
16
19. ● Lead Time:
○ Time it takes from Requirement state to Done State. i.e it
starts even before it comes to ToDo state.
● Cycle Time:
○ Time it takes from ToDo to Done State.
● The basic idea is to optimize the process so that the lead time
is small.
Measure the Cycle Time / Lead time :
The Flow
19
33. Step-1 : Start with a Kanban Board and add
Product Backlog to it
33
34. The Product Backlog for Scrumban
● Product backlog of Scrumban is similar to that of Scrum and can be owned
by a Product Owner.
● There is no (WIP) work in progress limit for Product Backlog. Let it come
● Can be prioritized, can be written in the form of User Stories/ Task
● Estimations can be done in Story Points / Man hours / T-shirt size of
S/M/L
34
35. Release Planning : Release Product
Backlog
● Use Product Backlog for Release Planning
● Planning should be done for upcoming
releases
● Appropriate duration should be around 3 (+-
) months
35
38. Planning On Demand
● No Sprint planning is done to bring the items from Release Product
Backlog to TODO list.
● Based on the capacity of TODO list, the items from Release Product
Backlog will move to TODO list based on
○ Priority
○ Product Owner Choice
○ Business requirements
○ Technical Requirements
● Of course a small planning is required :) but it's not as elaborate as Sprint
Planning.38
44. 33 - 50% time spent already Spent : Prune
Release Product Backlog
● Remove items which cannot be done in this release.
44
45. 66 - 75% time spent already Spent : Feature
Freeze and start of Release Stabilization
● Post feature freeze, team shall not take any new items even if it’s there in
ToDo list. The remaining item should go back to Product Backlog.
● Only stabilization related changes shall be allowed at this stage
● The Scrumban board shall be converted in Stabilization Board
● Stabilization board may or may not have WIP limit. All team memebers are
working towards same goal
45