Professional Documents
Culture Documents
2
Company Overview
3
Overview
What is Kanban, and how does it compare Scrum?
Where do they complement each other?
Are there any potential conflicts between the two?
Where Kanban is suggested to use?
4
Scrum in a nutshell
Split the organization into small teams
7
Kanban in a nutshell
Visualize the workflow, split the work in pieces and write each item on a card
10
Scrum is more prescriptive than Kanban
Agile methods are lightweight methods.
Scrum and Kanban are both highly adaptive
11
Roles
Scrum Prescribes Roles
13
Scrum & Kanban Board
Same Boards, whats the difference?
Scrum Limits WIP per Iteration
Kanban limits WIP per workflow
14
Both Limit WIP by different ways
15
Both are empirical
Direct Controls, is this possible?
Indirect Controls
16
Changes in Scrum and Kanban
What if someone turns up and wants to add E on the board?
17
Working Boards
Scrum Board is reset between each Iteration
18
Cross-Functional Teams
Scrum Prescribes Cross Functional Teams
19
Backlog
Both are based on incremental development, i.e. break the work into smaller pieces
Scrum Backlog must fit in a Sprint
Kanban team try to minimize lead time and Level the Flow
20
Estimations & Velocity
Scrum Prescribes Estimation & Velocity
21
Both allow working on multiple products simultaneously
Think of Product Backlog more like a Team Backlog
22
Both allow working on multiple products simultaneously
One strategy would be to have the team focus on one product per sprint
23
Both allow working on multiple products simultaneously
Another strategy would be to have the team work on features from both
products each sprint
24
Both allow working on multiple products simultaneously
We can have several products flowing across the same board.
25
Both allow working on multiple products simultaneously
26
Prioritized backlog
Scrum prescribe Prioritized PBIs
Kanban doesnt Prescribe Prioritized PBIs
you can choose any prioritization scheme (or even none)
Always take the top item.
Always take the oldest item (so each item has a timestamp).
Take any item.
Spend approximately 20% on maintenance items and 80% on
new features.
Split the teams capacity roughly evenly between product A and product B.
Always take red items first, if there are any.
27
Daily meetings
Scrum prescribes Daily Standups
People Oriented
Kanban doesnt prescribe Daily Standup
Board Oriented
28
Measure Progress
In Scrum, burn down charts are prescribed
29
Which one to pick?
Learn lessons from both models, and adapt them to fit the unique needs of
your organization.
30
Summary of Scrum vs. Kanban
Both are Lean and Agile.
Both use pull scheduling.
Both limit WIP.
Both use transparency to drive process improvement.
Both focus on delivering releasable software early and often.
Both are based on self-organizing teams.
Both require breaking the work into pieces.
In both, the release plan is continuously optimized based on Empirical data (velocity /
lead time).
31
Questions & Answers
Please go ahead
32