Why both scrum and lean in dist dev 07092010

2,596 views

Published on

Why both Lean and Agile in outsourcing and why Scrum is not enough

Why both scrum and lean in dist dev 07092010

  1. 1. Why both Lean and Agile in outsourcing Why Scrum is not enough Mads Troels Hansen September 2010 Tema: “Vandfaldmodeller, Scrum og Kanban i Offshoring”
  2. 2. Why both Lean and Agile in outsourcing Why Scrum is not enough <ul><li>Agenda </li></ul><ul><li>Some Lean and Agile definitions </li></ul><ul><li>4 Challenges with outsourcing and scaling </li></ul><ul><li>Patterns for successful distributed development </li></ul><ul><li>3 recommended actions for next step </li></ul><ul><li>Your expectations? </li></ul>
  3. 3. Selected Waterfall cases I will include <ul><ul><li>From CMMI to Lean, Scrum and Agile, SoftwarePeople (Bangladesh) </li></ul></ul><ul><ul><ul><li>From Waterfall to Agile ( http://bit.ly/cmmileanagile ) </li></ul></ul></ul><ul><ul><li>Large product with Waterfall, Anonymous (Pakistan) </li></ul></ul><ul><ul><ul><li>Problems with Waterfall </li></ul></ul></ul><ul><ul><li>From waterfall to Lean and Agile, Anonymous (India) </li></ul></ul><ul><ul><ul><li>From Waterfall to Lean and Agile </li></ul></ul></ul>
  4. 4. First some Definitions Scrum Waterfall Lean Kanban
  5. 5. Scrum <ul><li>Sprint Planning </li></ul><ul><li>Prioritization </li></ul><ul><li>Task breakdown </li></ul><ul><li>Team commitment </li></ul><ul><li>Sprint backlog </li></ul><ul><li>Daily Scrum Meeting </li></ul><ul><li>10-15 minutes </li></ul><ul><li>Three questions </li></ul><ul><li>Burndown Charts </li></ul><ul><li>Sprint </li></ul><ul><li>Release </li></ul><ul><li>Sprint Review </li></ul><ul><li>Demo </li></ul><ul><li>Product Owner </li></ul><ul><li>Prioritization </li></ul><ul><li>Voice of the Customer </li></ul><ul><li>Owns the product backlog </li></ul><ul><li>Scrum Master </li></ul><ul><li>Responsible for process </li></ul><ul><li>Support of team </li></ul><ul><li>Remove empediments </li></ul><ul><li>Scrum Team </li></ul><ul><li>Cross-functional </li></ul><ul><li>Deliver each sprint </li></ul><ul><li>Sprint Retrospective </li></ul><ul><li>Continuously improve </li></ul>
  6. 6. Schedule large work orders and align resources by workflow Schedule small work orders and align resources by schedule Schedule small work orders and align resources by workflow Waterfall – plan driven Agile – team oriented Lean – end2end
  7. 7. Lean 5 principles
  8. 8. Lean Software principles Poppendieck <ul><li>Eliminate Waste </li></ul><ul><li>Build Quality In </li></ul><ul><li>Learn Before Commitment </li></ul><ul><li>Deliver Fast </li></ul><ul><li>Improve Relentlessly </li></ul><ul><li>Respect People </li></ul><ul><li>Appreciate the System </li></ul>
  9. 9. Kanban development <ul><li>A very simple tool </li></ul><ul><ul><li>Manage the Workflow </li></ul></ul><ul><ul><li>Limit WIP </li></ul></ul><ul><ul><li>Visualize the work </li></ul></ul><ul><ul><li>Establish a cadence </li></ul></ul>Prescriptive Adaptive Kanban SCRUM Extreme Programming RUP Waterfall ” Whatever ”
  10. 10. <ul><li>The origin of kanban </li></ul><ul><li>Toyota Production System (TPS) </li></ul><ul><li>Taiichi Ohno ( 大野 耐 ) </li></ul><ul><li>A kan-ban </li></ul><ul><ul><li>A physical card (kan) </li></ul></ul><ul><ul><li>A signaling device (ban) </li></ul></ul>
  11. 11. <ul><li>Lean (TPS) and Kanban </li></ul>
  12. 12. <ul><li>Why Kanban? </li></ul>A Kanban system , starts to focus on flow and cycle time of delivered work and gives a way to visualize and resolve bottlenecks
  13. 13. 4 CHALLENGES
  14. 14. Length of Feedback Cycle
  15. 15. Don't go for the big BANG Build in small steps
  16. 16. What is done - legacy
  17. 17. What you do How you do it
  18. 18. 3 RECOMMENDED ACTIONS
  19. 19. 1. Do a Lean-Agile assessment
  20. 20. 2. Do Value Stream Mapping
  21. 21. 3. Do Regular retrospectives, USE DATA Collect and analyze data. 5xWhy, Systems Thinking, Cause and Effect
  22. 22. Patterns for successful distributed development Global Structure & Process Global Rhythm Global Req. Management Global Communication Protocols Global Technical Infrastructure Global Domain Knowledge Global Development Practices Cross cultural understanding <ul><li>Global value streams </li></ul><ul><li>Daily accountability </li></ul><ul><li>Retrospectives and problem solving </li></ul><ul><li>Regular Business feedback, iterations </li></ul><ul><li>Regular Delivery of releases, iterations </li></ul><ul><li>Continuous integration, daily check-in </li></ul><ul><li>Easy to access </li></ul><ul><li>Standard procedures </li></ul><ul><li>Automated and simple </li></ul><ul><li>Define Done, Done </li></ul><ul><li>Use Feature teams </li></ul><ul><li>Test first and automated </li></ul><ul><li>What you don’t know you don’t know </li></ul><ul><li>Tell the vision with stories and personas </li></ul><ul><li>Requirements with needs not solutions </li></ul><ul><li>Solve problems together </li></ul><ul><li>Global Ambassadors </li></ul><ul><li>Knowledge Sharing </li></ul><ul><li>Plan on different levels </li></ul><ul><li>JIT Requirements </li></ul><ul><li>Two phase commit </li></ul><ul><li>Establish a Toolbox (plan A, B, C) </li></ul><ul><li>Define regular meetings with purpose and owners </li></ul><ul><li>Daily communication with Video </li></ul>Mads Troels Hansen, 2010 <ul><li>Management System </li></ul><ul><li>Gemba walk </li></ul><ul><li>Systems Thinking </li></ul><ul><li>Rapid Response System </li></ul>
  23. 23. <ul><li>Thank you </li></ul><ul><li>[email_address] </li></ul>People don ’ t resist change, they resist being changed. - Peter Scholtes @MadsTH
  24. 24. Lean-Agile Thinking ApS Selected Solutions [email_address] , +45 6082 2282 Project Booster Accelerated Product Management Successful Outsourcing – 8 patterns Tuning & Improving Shared Product Vision Iterative Delivery Visual Mgt., Progress Planning [User Story Mapping, Personas] [Iterations, Stories, Tasks, Est.] [Task Board, Kanban, Scrum, Charts] [Release Mgt, Risks] Product Definition Product Delivery Delivering Business Value [Innovation Games] [Portfolio, Release Mgt.] [Backlog Grooming, Kano Model] High Productivity, Visibility Train the Trainers Business Training Improvement, Readiness [Implementing Offshore Patterns] [Train/Coach Teams] [Talks, Business Case] [Offshore Assessment] Reflection, Problem Solving High Business Value Improvement, Readiness Training with Games [Retrospectives] [Value Stream Mapping] [Assessment] [Kanban, Bottleneck, Business Value] Coaching Mentoring Assessment Workshops Talks Training

×