Kanban for software Development – Get more with less
Manoj K G Founder and Director, TeamSuccesso
1
Reference
2
Agenda
• History of Kanban
• Lean principles
• Introduction to Kanban
• Practices in Kanban
• Kanban for event driven development
• Advantages with Kanban
• Implementing Kanban
3
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
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
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
Lean principles
7
Agile Software Methodologies
8
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
Stop starting and start finishing!
Core practices in Kanban
1. Visualize
2. Limit Work-In-Progress
3. Manage Flow
4. Make Process policies explicit
5. Improve Collaboratively
11
Visualize your work flow12
Throughput
Capacity Productivity13
Limit your WIP
14
WIP
15
Lead time
16
Make Process policies explicit
Define classes of service - Defined based on business impact
17
Expedite
PoliciesLimit WIP to 1Time to deliver < 24 HrsNo misses e.g.: Production critical issues
Fixed delivery date
PoliciesDelivery before due date99 % on time deliverye.g.: Feature to support an event, compliance related changes
Standard classPolicies4 week lead time for complex issues2 week lead time for simple issue85% on time delivery e.g. change requests, enhancement requests
Intangible
Policies
e.g.: Version upgrades
18
Kanban for Event driven software development
19
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
• Helpdesk/Support activities (Initiated by an event, under SLA)
21
Application support and maintenance
22
Market driven software development
23
Advantages with Kanban
24
Teamwork
Encourages Swarming -leading to collaboration
25
kaizen culture
26
Implementing Kanban
27
Thank you
Mail- [email protected]
Blog - www.techbudha.com
LinkedIn - http://www.linkedin.com/pub/manoj-k-g/12/811/495 28
Top Related