Kanban is a lean methodology originally used in Toyota's production system to visualize workflow and limit work-in-progress. It has since been adapted for software development to optimize flow and delivery of value to customers. The core Kanban practices include visualizing the workflow, limiting work-in-progress, managing flow, making process policies explicit, and improving collaboratively. Implementing Kanban for software development can provide advantages like increased teamwork, collaboration, and continuous process improvement through a kaizen culture.

1. Kanban for software Development –
Get more with less
Manoj K G
Founder and Director, TeamSuccesso
1

2. Reference
2

3. Agenda
• History of Kanban
• Lean principles
• Introduction to Kanban
• Practices in Kanban
• Kanban for event driven development
• Advantages with Kanban
• Implementing Kanban
3

4. Kanban
Source: http://www.infoq.com/articles/hiranabe-lean-agile-kanban
• originates from Japanese, and translates roughly as "signboard.
• usually a physical card in a clear plastic envelope that instructs the
moving or creating of parts in a "pull" production system
4

5. Kanban in Toyota Production System (TPS)
http://www.toyotatr.com/?m=p&pid=19
Pull system - eliminates waste of waiting and waste of overproduction
5

6. Kanban in Toyota Production System (TPS)
Source: http://www.infoq.com/articles/hiranabe-lean-agile-kanban
Pull system - eliminates waste of waiting and waste of overproduction
6

7. Lean principles
7

8. Agile Software Methodologies
8

9. The Kanban method, as formulated by David J. Anderson, is an approach to
incremental, evolutionary process and systems change for
organizations.
a way to organize the chaos by making the need for prioritization and focus clear.
a way to uncover workflow and process problems so you may solve them in
order to deliver more consistently to your client/customer/etc.
Kanban accomplishes these things by introducing constraints into the system to
optimize the flow of value.
Flow is king. http://www.everydaykanban.com/what-is-kanban/
9

10. Stop starting and start
finishing!

11. Core practices in Kanban
1. Visualize
2. Limit Work-In-Progress
3. Manage Flow
4. Make Process policies explicit
5. Improve Collaboratively
11

12. Visualize your work flow
12

13. Throughput
Capacity Productivity
13

14. Limit your WIP
14

15. WIP
15

16. Lead time
16

17. Make Process policies explicit
Define classes of service
- Defined based on business impact
17

18. Expedite
Policies
Limit WIP to 1
Time to deliver < 24 Hrs
No misses
e.g.: Production critical
issues
Fixed delivery date
Policies
Delivery before due date
99 % on time delivery
e.g.: Feature to support an
event, compliance related
changes
Standard class
Policies
4 week lead time for
complex issues
2 week lead time for
simple issue
85% on time delivery
e.g. change requests,
enhancement requests
Intangible
Policies
e.g.: Version upgrades
18

19. Kanban for Event driven
software development
19

20. Some characteristics of Event Driven Development
• Rapidly changing priorities
• Increase in the waste with too many stories for the development
• The need for faster feedbacks - Shorter releases
20

21. • Helpdesk/Support
activities (Initiated by an
event, under SLA)
21

22. Application support and maintenance
22

23. Market driven software development
23

24. Advantages with Kanban
24

25. Teamwork
Encourages Swarming -leading to collaboration
25

26. kaizen culture
26

27. Implementing Kanban
27

28. Thank you
Mail- manojwky@gmail.com
Blog - www.techbudha.com
LinkedIn - http://www.linkedin.com/pub/manoj-k-g/12/811/495
28