The document outlines the importance of using a Minimum Viable Product (MVP) approach for implementing DevOps in organizations, highlighting the dangers of a big bang deployment. It discusses how a DevOps MVP can minimize risks, deliver business value, and improve processes through an incremental and iterative approach. Key advantages of this method include rapid feedback, issue identification, and building team confidence, while also identifying common pitfalls to avoid.

1. DevOps MVP
AgileWorks Copyright 2018
AgileWorks

2. Tim Guay, Agile Coach and Trainer
•Agile Practitioner since 2002
•PMP, CSM, CSD, CSP-SM, PMI-ACP, ICP-FDO, ICP-ASD, etc….
•Sits on the ICAgile DevOps Track Certification Committee
•Authored multiple Lean and Agile courses
•Clients include; JP Morgan Chase, Citigroup, Accenture, Cisco, Intuit,
Comcast, State of Washington, and the Royal Canadian Navy ( to
name a few).
tim@agileworksinc.com www.agileworksinc.com
AgileWorks Copyright 2018

3. Objectives
Provide a broad understanding of;
The dangers of a Big Bang DevOps Implementation
Using a MVP to drive a DevOps pilot
Advantages of using an MVP
What makes a good DevOps MVP
Antipatterns
AgileWorks Copyright 2018

4. The Problem
AgileWorks Copyright 2018

5. Dangers of Big bang
AgileWorks Copyright 2018
• People
• Process
• Business
• Technology

6. Is it Worth Betting the Farm?
AgileWorks Copyright 2018

7. How Do You Eat an Elephant?
AgileWorks Copyright 2018

8. What is a DevOps MVP?
Deliver business value
Prove out your pipeline
Flush out issues
Manage risk
Incremental and iterative migration
AgileWorks Copyright 2018

9. Using a MVP to drive a DevOps pilot
People
Process
Business
Technology
AgileWorks Copyright 2018

10. DevOps MVP vs. MVP
Conceptually the same, but…
Vanilla MVP doesn’t care how it is built
DevOps MVP totally cares
May need more than one
AgileWorks Copyright 2018

11. Goals of using a DevOps MVP
Minimize risk with rapid feedback while…
Visualizing
Optimizing
Aculturating
Automating
Delivering
AgileWorks Copyright 2018

12. Advantages of using an MVP
Easy to sell
Fails fast
Flushes out issues
Builds capability
Builds confidence
Boils a pot not an ocean
AgileWorks Copyright 2018

13. What makes a good DevOps MVP
Delivers real value to the customer
Everybody at the table
Exercises the entire pipeline
A Minimal Viable Process
Validates our DevOps architecture
Wins hearts and minds
AgileWorks Copyright 2018

14. Creating a DevOps MVP
Look for a low hanging fruit pilot
Adress cultural issues
Address process issues
Train team
Create a Minimal Viable Pipeline
Lots of telementry
AgileWorks Copyright 2018

15. Antipatterns
Pay lip service to the business value
Overfocus on the tooling
One MVP to test it all
MVP not viable
Can’t call the baby ugly
AgileWorks Copyright 2018

16. Then What!
Discuss Learnings
Persist or Pivot
Address Issues
Refactor your pipeline
Launch another DevOps MVP
AgileWorks Copyright 2018

17. AgileWorks Copyright 2018