Kanban is a lean methodology for managing workflow. It originated from the visual cards system used in 1940s Japanese auto manufacturers to optimize factory workflow. The key principles of Kanban include starting with the current process, pursuing incremental changes, respecting existing roles and responsibilities, and encouraging leadership at all levels. The key properties are visualizing work, limiting work-in-process, managing flow, and continuous improvement. Teams get started with Kanban by creating boards with columns and cards to visualize workflow.
2. Agenda
● Who am I?
● A bit of 1940s
● Kanban
○ What? Why?
○ Principles
○ Properties
○ Getting Started
2
○ Our Team
○ Scrum x Kanban
○ Tools
● References
● Q & A
3. Software Engineer
Passionate Hacker
ArchLinux Zealot
FOSS Enthusiast
I’m fond of doing
things that last
and all that jazz.
Lucas Lira Gomes
3
contact@x8lucas8x.com
linkedin.com/in/x8lucas8x
facebook.com/x8lucas8x
youtube.com/X80lucas08X
twitter.com/x8lucas8x
x8lucas8x.com
github.com/x8lucas8x
13. What is Kanban?
“Kanban is an approach to change
management. It isn’t a software
development or project management
lifecycle or process.”
David J. Anderson
13
14. Why Kanban?
● Simple visual approach
● Minimal entry barrier
○ 4 principles
○ 4 properties
● Easy to integrate
○ It is not a process
14
16. Kanban’s Principles
● How to think
○ Start with what you do now
○ Agree to pursue incremental, evolutionary change
○ Respect the current process, roles, responsibilities &
titles
○ Encourage acts of leadership at all levels
16
19. Kanban’s Principles
● Respect the current process, roles, responsibilities &
titles
○ Preserve what works
○ Altering the whole process is burdensome
19
20. Kanban’s Principles
● Encourage acts of leadership at all levels
○ Manager != Leader
○ Foster continuous improvements
■ Not a management activity
■ Kanban method is no exception
20
26. Kanban’s Properties
● Continuous Improvement
○ Evolution, not revolution
■ “Baby steps to awesomeness”
○ Make educated changes
■ Lead Time
■ Cycle Time
■ Throughput
■ Card distribution
26
27. Kanban’s Properties
● Continuous Improvement
○ Make educated changes
■ Features x Bugs
■ Blocked tasks over time
■ Unplanned tasks over time
■ ...
27