How we introduced and implemented Kanban for both a software and a system engineering team @ nine.ch, a leading provider for managed Linux server in Switzerland.
2. INITIAL SITUATION
• work overload
• too much simultaneous work in progress
• unclear priorities
• undefined cycle times
things just happened … somehow
3. REQUIREMENTS
• we didn’t want to turn everything upside
down
• evolutionary change process towards a
sustainable system
5. SCRUM
• too many prerequisites
• time boxing doesn’t work well with day-to-
day work
6. THE KANBAN METHOD
1. Start with what you do now.
2. Agree to pursue incremental, evolutionary
change.
3. Respect the current process, roles,
responsibilities & titles.
24. EXPERIMENT
• Time yourself counting from 1 to 26.
• Time yourself saying the alphabet a to z.
• Add up the times.
• Now time yourself counting from 1 to 26
while alternating saying the alphabet, so 1, a,
2, b, 3, c, etc.
• Were you faster at saying each sequence
individually or when you alternated?
33. POLICIES
• write them down and repeat them often!
• examples:
– orders are delivered the next business day
– bugs have higher priority than features
• Open Prio Meetings
http://www.lkce13.com/app/download/8243817195/Jimdo_Booklet_English.pdf
35. “Not every change is an improvement,
but every improvement is necessarily
a change”
Eliezer Yudkowsky
36. IMPROVE
• small continuous, incremental and
evolutionary changes that stick
• shared understanding of theories about
work, workflow, process, and risk
• feedback loops
37. KAIZEN: CONTINUOUS IMPROVEMENT
• Open Prio Meetings
http://www.lkce13.com/app/download/8243817195/Jimdo_Booklet_English.pdf
• regular team retrospectives
• small incremental improvements
• some ideas may result in bigger projects
38. CORE VALUES
STRATEGY, ALIGNMENT AND CULTURE
• The Boy Scout Rule
• Zero Waste
• Consistency
• Explicitness over Implicitness
• YAGNI, You Ain't Gonna Need It
• DRY, Don’t Repeat Yourself