Waterfall-ITIL vs Agile-DevOps
Embed Size (px)
Transcript of Waterfall-ITIL vs Agile-DevOps
- 1.Waterfall-ITIL vs. Agile-DevOpsSimple lessons from Frankenstein and Star Trek By Paul Peissner
2. Waterfall & Frankenstein 3. Waterfall has many high-risk & hard-toexplain complexities under the covers 4. Historically, it has proven to beslow, unreliable & disappointing 5. And it appears almost miraculous if you can make it workIts s Alive! 6. Yes, it is working! But is itrepeatable or sustainable? 7. Development does not want tolook at it after Ops releases it! 8. Waterfall-ITIL struggle withChange Management flexibility 9. You are my creator, but now I am your master! 10. Agile & Tribbles 11. Agile is so small, cute,cuddly and harmless 12. Agile appears so friendly thateveryone wants one today 13. But Agile can overwhelm Ops & AssetManagement practices pretty quickly 14. And Agile can create newbusiness problems too.. 15. Change CommitteeITIL and Asset Managementalways expected Waterfall Apps!- Millions of Code lines Asset- Thousands of contributors- Hundreds of featuresDeveloper- Over many years- Big and disruptive!DevOps and Asset Managementalways expecting Agile Apps! - 10s of Code lines - With more Common/Repeatable Services - Infrastructure & Deployment as Code - 5-7 Micro teams - How big is your pizza? How many teams needed? - Code as AssetCode Reuse as a standard. - 3-7 Features - Fewer moving parts, more code IP to protect - Over 3-6 weeks - Faster moving process, to grow the business - Small and invisible! 16. Now lets talk about DevOps (Agile Dev and Best-practice Ops) 17. But some Dilbert Advice to considerbefore we get started Waterfall experience DevOpsWaterfall Brain.