Why DevOps is perfect for Modern IT organizations leveraging Agile and Why Waterfall is perfect for Legacy IT ITIL organizations

1. Waterfall-ITIL vs. Agile-DevOps
Simple lessons from Frankenstein and Star Trek
By Paul Peissner

2. Waterfall & Frankenstein

3. Waterfall has many high-risk & hard-to
explain complexities under the covers

4. Historically, it has proven to be
slow, unreliable & disappointing

5. And it appears almost miraculous if you can make it work
It’s s Alive!

6. Yes, it is working! But is it
repeatable or sustainable?

7. Development does not want to
look at it after Ops releases it!

8. Waterfall-ITIL struggle with
Change 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 that
everyone wants one today…

13. But Agile can overwhelm Ops & Asset
Management practices pretty quickly…

14. And Agile can create new
business problems too..

15. Change Committee
ITIL and Asset Management
…always expected Waterfall Apps!
- Millions of Code lines Asset
- Thousands of contributors
- Hundreds of features
Developer
- Over many years
- Big and disruptive!
DevOps and Asset Management…always expecting Agile Apps!
- 10’s 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 Asset…Code 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 let’s talk about DevOps
(Agile Dev and Best-practice Ops)

17. But some Dilbert Advice to consider…
before we get started…
Waterfall experience
DevOps
Waterfall Brain.