Waterfall-ITIL vs. Agile-DevOps

Simple lessons from Frankenstein and Star TrekBy Paul Peissner

Waterfall & Frankenstein

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

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

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

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

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

Waterfall-ITIL struggle with Change Management flexibility

“You are my creator, but now I am your master!”

Agile & Tribbles

Agile is so small, cute, cuddly and harmless…

Agile appears so friendly that everyone wants one today…

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

And Agile can create new business problems too..

- With more Common/Repeatable Services- Infrastructure & Deployment as Code

- How big is your pizza? How many teams needed?- Code as Asset…Code Reuse as a standard….

- Fewer moving parts, more code IP to protect

- Faster moving process, to grow the business

ITIL and Asset Management…always expected Waterfall Apps!- Millions of Code lines- Thousands of contributors- Hundreds of features- Over many years- Big and disruptive!

DevOps and Asset Management…always expecting Agile Apps!- 10’s of Code lines

- 5-7 Micro teams

- 3-7 Features

- Over 3-6 weeks

- Small and invisible!

Change Committee

Asset

Developer

Now let’s talk about DevOps(Agile Dev and Best-practice Ops)

But some Dilbert Advice to consider… before we get started…

Waterfall experience

DevOps

Waterfall Brain.