Learn about the main important steps you should pay attention to when you start using Kanban in your software development process.

1. A recipe for success
Kanban - Chapter 3

2. Overview
1.Increase quality
2.Reduce WiP
3.Deliver frequently
4.Balance demand and throughput
5.Prioritize
6.Increase predictability

3. Increase quality
• Reason
• bugs = biggest waste in software development
• consistent good quality strengthen trust
• trust = political capital

4. Increase quality
• Methods
• testing (QA, TDD)
• code reviews
• design patterns
• modern software development tools
• reduce WIP

5. Reduce WIP
• more WIP increases lead time
• longer lead times = worse quality
• Quality and WIP are strongly connected, they
should be implemented at the same time

6. Deliver frequently
• frequent small gestures are better than
infrequent large gestures
• small scale actions usually only entail small
costs
• builds trust with upstream partners/customers

7. Balance demand and
throughput
• The point is
• shows bottlenecks
• allowes to give the employees a free hand - Kaizen
cultur
• How?
• pull system regulates throughput
• political capital can be used to manage demand

8. Prioritize
• Reason
• increases delivered business value
• How?
• requires trust from upstream partners/customers
• requires high predictability
• focus on business value, not amount of code

9. Increase predictability
• Motive:
• high variability leads to more WIP and longer lead times
• high variability correlates negatively with predictability
• How?
• requires a mature organization
• wise workers - agree and change their behavior

10. Conclusion
• WIP correlates with quality
• frequent deliveries and consistent high quality build trust
• pull system regulates demand and throughput
• good prioritization maximizes delivered business value
• confidence creates opportunities for improvement