Kanban
47
Kanban Paweł Brodzinski @pawelbrodzinski
-
Upload
pawel-brodzinski -
Category
Technology
-
view
3.144 -
download
4
description
Kanban is more and more popular approach among teams working on building software. At the same time it is probably the most light-weight approach which is applicable in such cases. What exactly Kanban is? How does it work? When, where and why it is worth to adopt it?The session describes basic rules of Kanban and explains when the method, or its elements, is worth applying in software development teams. Comparisons to both: formal approaches and agile methods, with special focus on Scrum, help to understand Kanban specifics and learn when it might be a suitable option for teams.
Transcript of Kanban
Kanban
Paweł Brodzinski
@pawelbrodzinski
About me
VSofthttp://vsoft.pl
BlogBloghttp://blog.brodzinski.com
Twitter@pawelbrodzinski
Where is Kanban from?
Kanban: ITEMITEMITEMITEM NAMENAMENAMENAME
IDIDIDID PRIORITYPRIORITYPRIORITYPRIORITY
DUEDUEDUEDUE DATEDATEDATEDATE
DATEDATEDATEDATE FROMFROMFROMFROM
DATEDATEDATEDATE TOTOTOTO
Kanban is an approach to change
management. It isn’t a software
development or project management
lifecycle or process.lifecycle or process.
David Anderson
Kanban
Visualize workflow
Limit WIP (Work In Progress)
Manage flowManage flow
Make policies explicit
Improve collaboratively
Kanban
Start with what you have
Agree to pursue incremental,
evolutionary change
Respect current environment (process,
responsibilities, roles, etc.)
Scrum versus Kanban
Scrum versus Kanban
Team
POPOPOPOSMSMSMSMTEAMTEAMTEAMTEAM
Scrum versus Kanban
Process
Scrum versus Kanban
Time boxing/cadence
Release Retro Planning
Kanban
Start with what you have
Agree to pursue incremental,
evolutionary changeevolutionary change
Respect current environment (process,
responsibilities, roles, etc.)
Kanban + PMBOK?
Kanban
Visualize workflow
Limit WIP
Manage flowManage flow
Make policies explicit
Improve collaboratively
World steering center
The simplest Kanban board
TO DOTO DOTO DOTO DO ONGOINGONGOINGONGOINGONGOING DONEDONEDONEDONE
2222
Kanban boardTO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
2222 3333 3333 2222
Hand-offsTO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
2222 3333 3333 2222
Who does what?TO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
2222 3333 3333 2222
BlockersTO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
2222 3333 3333 2222
Classes of serviceTO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
2222 3333 3333 2222
WORKWORKWORKWORK ITEMITEMITEMITEM
IDIDIDID
ITEMITEMITEMITEM NAMENAMENAMENAME
IDIDIDID PRIORITYPRIORITYPRIORITYPRIORITY
DUEDUEDUEDUE DATEDATEDATEDATE
DATEDATEDATEDATE FROMFROMFROMFROM
DATEDATEDATEDATE TOTOTOTO
ESTIMATEDESTIMATEDESTIMATEDESTIMATED
SPENTSPENTSPENTSPENT
SIZESIZESIZESIZE
Kanban
Visualize workflow
Limit WIP
Manage flowManage flow
Make policies explicit
Improve collaboratively
TO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
2222 3333 3333 2222
Kanban
Visualize workflow
Limit WIP
Manage flowManage flow
Make policies explicit
Improve collaboratively
5O5O5O5O5O5O5O5O
Why WIP limits?
5O5O5O5O5O5O5O5O
How to set limitsTO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
???? ???? ???? ????
WIP limits different wayTO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
Kanban
Visualize workflow
Limit WIP
Manage flowManage flow
Make policies explicit
Improve collaboratively
TO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
2222 3333 3333 2222
WIPWIPWIPWIP
START START START START HEREHEREHEREHERESTART START START START HEREHEREHEREHERE
You need team buy-in
Value stream mapping
TO DOTO DOTO DOTO DO ONGOINGONGOINGONGOINGONGOING DONEDONEDONEDONE
2222
Upstream/downstream process
Upstream/downstream processTO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
2222 3333 3333 2222
The simpler the better
One or many boards?
Alternative Kanban board designs
Kanban
Visualize workflow
Limit WIP
Manage flowManage flow
Make policies explicit
Improve collaboratively
What’s in it for me?
Everyday informed decisions
TO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
2222 3333 3333 2222
Behavior changes
TO DOTO DOTO DOTO DO DEVELOPMENTDEVELOPMENTDEVELOPMENTDEVELOPMENT DONEDONEDONEDONEBACKLOGBACKLOGBACKLOGBACKLOG TESTINGTESTINGTESTINGTESTING DEPLOYMENTDEPLOYMENTDEPLOYMENTDEPLOYMENT
ONGOING ONGOINGDONE DONE
LLLL
2222 3333 3333 2222
Best engineering practices
Continuous improvement
Thank you
Questions?
Paweł Brodzinski
blog.brodzinski.com
vsoft.pl
@pawelbrodzinski
