2. Agenda
High level overview of scrum
High level overview of Kanban
Work in progress
Scrum resists change during a sprint
Kanban focusses on continuous flow
Sprint vs continuous flow
Homogenous teams vs heterogeneous teams
Conclusion
EA
@
Work
www.eaatwork.be 2
3. High level view of Scrum
Minimal core principles
3 type of Roles
Product Owner
Scrum Master
Team members
3 type of Artifacts
Product backlog
Scrum backlog
Tasks
3 type of meetings
Sprint planning
Sprint review
Sprint retrospective
Time boxed iterations
Scrum consists out of a minimal set of practices
If you are not performing them all, do not call it scrum but call it differently like
“Scrummish” or “Scrumlike” or “Scrum inspired”
EA
@
Work
www.eaatwork.be 3
4. High level view of Kanban
Minimal core principles
Work in progress limit
Doing
Visualize your workflow Back log
2
Done
Limit your work in progress Pull
cts s
s ifa ng
ole art eti
dr d me
ibe r ibe ed
scr esc rib
pre pr esc Flow
No N o pr
No
Kanban is less prescriptive then Scrum and highly adaptable
Nothing prevents a Kanban team to use some principles of Scrum, XP or even RUP
Often the following principles are applied
Daily standup meeting
Kanban (Sprint) planning meeting
Operations review (Retrospective) meeting
EA
It is important that the “really used” workflow is presented on the kanban board @
Work
www.eaatwork.be 4
5. Work in Progress
Scrum: Limit the work per sprint (unit of
time) Product
Backlog
Sprint
Backlog
In progress Done
Backlog Item Ready
Backlog Item Ready
Sprint planning
Backlog Item Ready
Backlog Item Ready
Ready
Backlog Item
Ready
Priority
Backlog Item
Backlog Item
Backlog Item
Fixed work in progress for a sprint
Backlog Item
Kanban: Limit per worflow state
Doing Validate
Scheduled Done
4 2
Ready
Ready
Ready
Ready
Ready
EA
Ready
@
Work
www.eaatwork.be 5
6. Work in progress
Scrum allows to put everything in progress
at start of the sprint
Product Sprint
In progress Done
Backlog Backlog
Backlog Item in progress
Backlog Item in progress
Sprint planning
Backlog Item in progress
Backlog Item in progress
Backlog Item in progress
in progress
Priority
Backlog Item
Backlog Item
Backlog Item
Fixed work in progress for a sprint
Backlog Item
Kanban does not allow to exceed the WIP
Doing Validate
Scheduled Done
4 2
Ready in progress in progress Ready
Ready in progress Ready
Ready in progress
in progress
Not allowed
EA
@
Work
www.eaatwork.be 6
7. Scrum resists change
During a sprint the scope is fixed
No new tasks can be added, they will need to wait
until the next sprint
Product Sprint
In progress Done
Backlog Backlog
Backlog Item Ready
Backlog Item Ready
Sprint planning
Backlog Item Ready
Backlog Item Sprint planning determined the Ready
scope for the next 2 to 4
Backlog Item Ready
weeks depending on sprint
lenght Ready
Priority
Backlog Item
Backlog Item
Backlog Item
Urgent
During a sprint it is not allowed to change the scope
Backlog Item
In some organizations this is not acceptable! Scrum
teams plan a buffer to absorb the unplanned work
(based on the amount of unplanned work in
previous sprints) but this is a workaround. EA
@
Work
www.eaatwork.be 7
8. Kanban focus on continuous flow
Kanban focusses on continuous flow. New urgent work
can be added on the Kanban board at anytime point in
time.
Doing Validate
Scheduled Done
4 2
Urgent in progress in progress Ready
Ready in progress Ready
Ready in progress
Ready in progress
In case that the WIP limit is not exceeded the work
can be addressed immediately
Doing Validate
Scheduled Done
4 2
in Urgent
progress in progress Ready
Ready in progress Ready
Ready in progress
Ready in progress
EA
@
Work
www.eaatwork.be 8
9. Sprint (fixed time) vs continuous flow
Scrum works with sprints. After a sprint the
scrumboard is reset
Sprint Sprint Sprint Sprint
In progress Done In progress Done In progress Done In progress Done
Backlog Backlog Backlog Backlog
Ready Ready in progress Done Done Ready
Ready Ready in progress Done Ready
Ready in progress Done Ready
Ready Done Ready
Ready Done Ready
Ready Done Ready
Sprint A
Sprint B
Kanban does not get reset
Sprint In progress Sprint In progress Sprint In progress Sprint In progress
Done Done Done Done
Backlog 4 Backlog 4 Backlog 4 Backlog 4
Ready Ready in progress Done Ready in progress Done Ready in progress Done
Ready Ready in progress Done Ready in progress Done Ready in progress Done
Ready Ready in progress Ready Done Ready Done
Ready Ready Done Ready Done
Ready Done Ready Done
Ready Done Ready Done
Done
Done
Kanban supports tasks longer then a sprint
(but it takes up a precious slot of the WIP
EA
@
Work
www.eaatwork.be 9
10. Scrum works with selfcontained teams
Kanban allows to work with heterogeneous teams
Sprint
In progress Done
Scrum team need to be Backlog
Ready
selfcontained. Ready
Ready
All the different skills that are
Ready
Ready
Ready
needed to create the solution need
to be part of the scrum team. Only scrumteam can update scrumboard
Specific profiles or scares Scrum master
resources those people are Team member
allocated for a specific time. Speciality resource (only 20%)
Kanban team focusses on the
Doing Validate Test Scenario Test Execution
Scheduled Done
4 2 2 1
Ready in progress in progress in progress Ready
workflow and the tasks that need Ready
Ready
in progress
in progress
in progress Ready
Ready in progress
to occur.
A Kanban board can be owned by
a single team or by multiple teams
where a team can have ownership EA
on one or more workflow steps @
Work
Development Team Test Team
www.eaatwork.be 10
11. Conclusions
Kanban is less intrusive to introduce in an
organization.
Kanban has only a very small but very
powerfull guidelines
Can easily be adopted (does not modify
the process)
Kanban supports heterogeneous teams
Kanban does not prevent to use best
practices of Scrum etc like the daily
meeting.
EA
@
Work
www.eaatwork.be 11
