Lean , Pull System & Kanban |iZenBridge

2,305 views
2,042 views

Published on

Published in: Education
2 Comments
4 Likes
Statistics
Notes
No Downloads
Views
Total views
2,305
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
60
Comments
2
Likes
4
Embeds 0
No embeds

No notes for slide

Lean , Pull System & Kanban |iZenBridge

  1. 1. iZenBridge Pull Planning, Lean & Kanban Saket Bansal , PMP® , PMI-ACP® iZenBridge Consultancy Private Limited © 2013 iZenBridge | CONFIDENTIAL
  2. 2. Agenda • Lean Software Part 1 Development Principles Part 2 Part 3 • Pull System • Pull System in Action © 2013 iZenBridge | CONFIDENTIAL
  3. 3. The 7 Principles of Lean Software Development • • • • • • • Eliminate Waste Build Quality In Create Knowledge Defer Commitment Deliver Fast Respect People Optimize the Whole © 2013 iZenBridge | CONFIDENTIAL
  4. 4. Eliminate Waste Manufacturing Software Development In-Process Inventory Partially Done Work Over-Production Extra Features Extra Processing Relearning Transportation Handoffs Motion Task Switching Waiting Delays Defects Defects © 2013 iZenBridge | CONFIDENTIAL
  5. 5. Build Quality In Preventing defects Proactive Quality Assurance Test First Approach © 2013 iZenBridge | CONFIDENTIAL
  6. 6. Create Knowledge  Team Engagement Wiki Kaizen © 2013 iZenBridge | CONFIDENTIAL
  7. 7. Defer Commitment © 2013 iZenBridge | CONFIDENTIAL
  8. 8. Deliver Fast © 2013 iZenBridge | CONFIDENTIAL
  9. 9. Respect People © 2013 iZenBridge | CONFIDENTIAL
  10. 10. Optimize The Whole Inventories •Hide errors in the process •Hide misunderstandings •Hide poor design •Hide bugs.. © 2013 iZenBridge | CONFIDENTIAL
  11. 11. A Holistic View Business Management Delivery © 2013 iZenBridge | CONFIDENTIAL
  12. 12. forum.iZenBridge.com © 2013 iZenBridge | CONFIDENTIAL
  13. 13. Agenda • Lean Software Part 1 Development Principles Part 2 Part 3 • Pull System • Pull System in Action © 2013 iZenBridge | CONFIDENTIAL
  14. 14. It’s all about Scheduling ! © 2013 iZenBridge | CONFIDENTIAL
  15. 15. How to Schedule ? © 2013 iZenBridge | CONFIDENTIAL
  16. 16. Push Sheduling ES ES Analysis , Feature 1 Develop Feature 1 ES Test , F1 & F2 Start ES ES Analysis , Feature 2 Develop Feature 2 © 2013 iZenBridge | CONFIDENTIAL End
  17. 17. Challenges in Push Sheduling © 2013 iZenBridge | CONFIDENTIAL
  18. 18. Re-Planning …. • The old schedule was optimal based on old assumptions. • The new schedule should be optimized based on the new assumptions. • Managers, based on their personal knowledge, decide the next action. © 2013 iZenBridge | CONFIDENTIAL
  19. 19. Pull Scheduling © 2013 iZenBridge | CONFIDENTIAL
  20. 20. Toyota’s “Thinking Production System” “Under a ‘push’ system, there is little opportunity for workers to gain wisdom because they just produce according to the instructions they are given,” he says. “In contrast, a ‘pull’ system asks the worker to use his or her head to come up with a manufacturing process where he or she alone must decide what needs to be made and how quickly it needs to be made.” Source http://www.toyotageorgetown.com/tpsoverview.asp © 2013 iZenBridge | CONFIDENTIAL Teruyuki Minoura
  21. 21. Pull Sheduling © 2013 iZenBridge | CONFIDENTIAL
  22. 22. forum.iZenBridge.com © 2013 iZenBridge | CONFIDENTIAL
  23. 23. Agenda • Lean Software Part 1 Development Principles Part 2 Part 3 • Pull System • Pull System in Action © 2013 iZenBridge | CONFIDENTIAL
  24. 24. Pull Scheduling for Software Projects Visualize the Flow …. Ready Develop Test Done Cycle Time Limit WIP Explicit Policies 1. Code 2.Integrate 3.Update Design © 2013 iZenBridge | CONFIDENTIAL 1. Test XYM 1. Migrate / Upgrade
  25. 25. System like Airport © 2013 iZenBridge | CONFIDENTIAL
  26. 26. Just in Time • • • • Don’t build features that nobody needs right now Don’t write more specs than you can code Don’t write more code than you can test Don’t test more code than you can deploy © 2013 iZenBridge | CONFIDENTIAL
  27. 27. Kanban • • • • Self-directing Details are on Card The kanban cards tell developers what to do Status is visible at a glance © 2013 iZenBridge | CONFIDENTIAL
  28. 28. Kanban Board Analyze (3) Develop (5) Analyze Feature Feature Ready for Release Accept (3) Ready (5) Dev Feature Feature Feature Feature Ready for Dev Ready for Accept Feature Feature Feature Feature Feature Feature Feature Columns For Each Work Type Feature Urgent Criteria •Design Complete •Acceptance Test Case Done •UX Input Ready •Code Complete •Source checked In •Unit Tests Green •Build Succeeds •Acceptance tests Green •PO Acceptance © 2013 iZenBridge | CONFIDENTIAL
  29. 29. Information Radiators / Visual control • Management by sight. • Must be able to see • • • • What is going on What needs to be done What problems exist What progress is being made • Work cannot be self-directing without appropriate visual controls • Examples: Lists of problems, Ideas for improvements, Candidates for refactoring, Progress made © 2013 iZenBridge | CONFIDENTIAL
  30. 30. Daily Meeting • • • • Cards alone are not enough A regular brief meeting helps make work self-directing The daily team meeting should be short (15 minutes) Everyone on the team should be there © 2013 iZenBridge | CONFIDENTIAL
  31. 31. forum.iZenBridge.com © 2013 iZenBridge | CONFIDENTIAL
  32. 32. Agenda • Lean Software Development Principles Part 1 Part 2 Part 3 • Pull System • Pull System in Action © 2013 iZenBridge | CONFIDENTIAL
  33. 33. Stay Connected Saket.Bansal@iZenBridge.com www.iZenBridge.com forum.iZenBridge.com Youtube LinkedIn Group www.youtube.com/izenbridge PMI-ACP: Agile Certification Made Easy © 2013 iZenBridge | CONFIDENTIAL

×