Lean part of DevOps - DevOps Amsterdam meetup - 17-8-2016
•Descargar como PPTX, PDF•
1 recomendación•488 vistas
Lean has a central place in DevOps - it's part of CALMS. And Lean is wider and broader than DevOps. And if we compare them, they reinforce each other.
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (20)
Similar a Lean part of DevOps - DevOps Amsterdam meetup - 17-8-2016
Similar a Lean part of DevOps - DevOps Amsterdam meetup - 17-8-2016 (20)
Último
Último (20)
Lean part of DevOps - DevOps Amsterdam meetup - 17-8-2016
- 1. @PavelChunyayev The Lean Part of DevOps Why are Lean ideas so crucial for DevOps culture? by Pavel Chunyayev, 18-8-2016 Amsterdam, Atlassian DevOps Amsterdam meetup
- 2. @PavelChunyayev Amsterdam Levi9 HQ Amsterdam – 2005 25 people Novi Sad Serbia Novi Sad – 2005 350+ people Zrenjanin Serbia Zrenjanin– 2014 50+ people Iasi Romania Iasi – 2007 100+ people Kyiv Ukraine Kyiv – 2008 160+ people Lviv Belgrade Ukraine Lviv– 2016 20+ people
- 3. @PavelChunyayev E-Retail Digital Marketing Traffic and Transport FinTech Software Services
- 4. @PavelChunyayev Customer satisfaction 2015 • 4th year great results in Outsourcing Performance study • 2015: 100% customer recommendation score Excellent trust score
- 5. @PavelChunyayev About me • 12 years of IT experience • Lived and worked in Ukraine and Estonia • Two years ago moved to the Netherlands • Love cycling • Love Dutch language • Love software development and delivery processes • Love working with people
- 7. @PavelChunyayev Continuous Delivery Plan Code Build Test Release OperateEnvision
- 9. @PavelChunyayev Keep the product releasable Build quality in
- 11. @PavelChunyayev • Culture • Automation • Measurement • Sharing
- 12. @PavelChunyayev • Culture • Automation • Lean • Measurement • Sharing
- 16. @PavelChunyayev Lean manufacturing - Principles • Elimination of waste • Continuous improvement • Respect for people • Pull instead of push • Just in time production • Quality built in
- 17. @PavelChunyayev Lean manufacturing – Forms of Waste • Mura – Waste because of variation • Muri – Waste because of unreasonable work • Muda – Waste that doesn’t add value
- 18. @PavelChunyayev Lean manufacturing – Types of Waste • Transportation • Waiting • Overproduction • Defects • Inventory • Movement • Extra processing
- 19. @PavelChunyayev Lean manufacturing – Metrics • Process time • Delay time • Lead time • % complete and accurate
- 21. @PavelChunyayev Lean thinking • Value • Value streams • Flow • Pull • Perfection • Build quality in • Understanding ‘takt’ time • Reducing batch sizes • Pull system • Continuous improvement • Focus on long-term goal
- 22. @PavelChunyayev Lean IT Goals: • Increase productivity • Increase customer benefits • Continuous improvement process
- 23. @PavelChunyayev Lean IT - Trends • Reducing costs (eliminating waste), six sigma • Transformation to utility • Outsourcing (e.g. Cloud)
- 24. @PavelChunyayev Conflict with DevOps? • Innovation and disruption vs Operational excellence • Experimentations vs Predictability • Unstructured and uncertain vs Standards and variation avoidance
- 25. @PavelChunyayev Lean and DevOps • It’s not only about costs • Continuous learning • Build quality in • Visualize • Think backwards from customer value • Not from current capabilities • Embrace uncertainty
- 27. @PavelChunyayev Lean software development - Principles • Eliminate waste • Amplify learning • Decide as late as possible • Deliver as fast as possible • Empower the team • Build quality in • Optimize for the whole
- 28. @PavelChunyayev Waste • Partially done work (Starting more than finishing) • Extra processes (Bureaucracy) • Extra features (Unnecessary code) • Task switching (Changing requirements and priorities) • Waiting (Delays in the development process) • Motion • Defects (Quality issues, rework)
- 29. @PavelChunyayev Amplify learning • Pair programming • Code reviews • Documentation • Wiki • Commented code • Knowledge sharing sessions • Training
- 30. @PavelChunyayev Decide as late as possible • For decisions that are irreversible or impractical to reverse • Keep the options for as long as possible • You will know a lot more by the time the decision needs to be made • Too early and you are limited by the choice you could have made without enough information
- 31. @PavelChunyayev Deliver as fast as possible • Continuous Delivery • DevOps • Agile methodologies • Shared responsibility
- 32. @PavelChunyayev Empower the people • Give responsibility to make decisions about their work
- 33. @PavelChunyayev Build quality in • Andon – stop the line • Pair programming • Test driven development • Constant feedback • Minimize handovers (time between stages) • Continuous integration • Automation
- 34. @PavelChunyayev Optimize for the whole • Optimize for the whole, not specific departments or teams • E2e process with focus on customer needs • Prefer product orientation vs project orientation • Focus on quality and innovation, not on quick execution
- 35. @PavelChunyayev Problems of Lean • Focus on tools, not on the philosophy and culture • Decide on the solution without understanding true problem • Cargo cult
- 36. @PavelChunyayev Lean software development - Principles • Eliminate waste • Amplify learning • Decide as late as possible • Deliver as fast as possible • Empower the team • Build quality in • Optimize for the whole
- 37. @PavelChunyayev Lean Startup / Lean Enterprise
- 38. @PavelChunyayev
- 40. @PavelChunyayev Generate Waste Excercise • Variation • Unreasonable work • Non-value adding processes
- 41. @PavelChunyayev Change the culture is the most important and the most hard part of Lean
- 42. @PavelChunyayev Change the culture is the most important and the most hard part of Lean and DevOps
- 43. @PavelChunyayev Summary Empower the people Build quality in Eliminate the waste Change the culture Plan Code Build Test Release OperateEnvision
- 44. @PavelChunyayev Thank you :) Empower the people Build quality in Eliminate the waste Change the culture +31 6 2117 5817 pavel@levi9.com Plan Code Build Test Release OperateEnvision
Notas del editor
- Questions are welcome during the talk. Disagreement is welcome, but after the talk. Yes, but; what if. Interactive – raise hand, provide feedback – tweet.
- Over 700 employees now Picture of Belgrade is pending
- .we develop core software for (and with) these companies
- .
- .
- Streamlining and flow Customer focus Unesed features Time to market
- It’s all about quality. Increasing speed by ensuring quality - positive feedback loop
- .
- .
- .
- .
- .
- Henry Ford No variety (one model, one color) - 19 years Toyota production system Kaizen – continuous improvement Just in time Jidoka - automation
- Principles Plan – Do – Check – Act
- .
- Muri – stressing or overburdening the people, equipment or system Muda – type 1 – non-value adding, but necessary for the system. Reduce until you can eliminate Muda – type 2 – non-value adding and unnecessary. Eliminate first!
- .
- Plan Create a plan, define steps, predict results of the change Do Execute the plan on a small scale or in a test environment. Check Examine the results. Decide whether to continue or try again. Act Implement the change on the broader scale or further.
- .
- Manufacturing business services based on lean ideas Better align IT with business
- .
- .
- Mary and Tom Poppendieck
- .
- First way of DevOps
- Third way of DevOps Sharing!
- . But not too late :)
- .
- .
- Second way of DevOps
- More sloppy code because of urgency Bigger utilization of departments (QA)
- .
- .
- MVP Build – Measure - Learn Validated learning
- MVP Build – Measure - Learn Validated learning
- .
- .