The document describes a role playing game to simulate a DevOps transformation. Players take on roles like developer, operations, business owner, etc. The game is played over 3 sprints where the teams start with separate development and operations teams, then integrate operations into development teams, and finally work to continuously deliver value through smaller batches and automated deployments. Bottlenecks are addressed and teams work to improve collaboration and feedback loops. The purpose is to demonstrate how DevOps principles can help organizations increase speed, stability, and innovation.

1. Dana
Pylayeva

2. Turn and Talk
What’s
your
name?
What’s
your
current
role?

3. Co-organizer
I am speaking:Author
Agile Coach,
CSM, CSPO, CSP,
TBR-CT Dana
Pylayeva
@DanaPylayeva
dpylayeva@gmail.com
NYC Scrum User Group
World Retrospective Day
Big Apple Scrum Day
ConTEST NYC by
Test Masters
Academy

4. Beware of
Goals Misalignment

5. Dev:
Focus
on
Speed
and
DeliveryDev Team

6. Ops
Team
Ops:
Focus
On
Stability
and
Reliability

7. Treplan
Tarch
review
T tech
debt
Tretest
Trework
Trebuild
Trefix
Trollback
Tre-
release
Goals Misalignment
Leads to a Low Trust
Culture
Source: Lee Reid http://devops.com/2015/06/22/the-simple-math-of-devops/

8. Source: Puppet Labs: State of DevOps Report 2017
DevOps: Increased Speed

9. DevOps: Increased Stability
Source: Puppet Labs: State of DevOps Report 2017

10. DevOps: Increased Innovation
Source: Puppet Labs: State of DevOps Report 2017

11. Sounds like Magic…

12. What’s Your Favorite
Definition of
DevOps?

13. My Favorite One
“A mix of patterns intended to
improve collaboration between
development and operations.
DevOps addresses shared goals
and incentives as well as shared
processes and tools.”
~ Michael Hüttermann

14. 2017 –
No Longer
For
Unicorns
Only:
Macy’s,
Nordstrom,
GE Capital, Disney,
US Department of
Homeland Security,
IBM, Microsoft,
Barclays Capital,
Capital One,
Target, Walmart,
1-800-Flowers…
2009 2011

15. DevOps Transformation
RPG

16. DevOps Transformation
Game Plan
Sprint 1: Feel the pain:
Cyclical Value Delivery with Scrum.
Sprint 2: First steps towards DevOps.
Sprint 3: Continuous Value Delivery.

17. Pick Your Role
and
Meet Your Team

19. Some Players Will Get Special
Instructions.
These Will Modify the Game!

20. Q: Will I need to ask
Benjamin Business what
needs to be built?
A: Yes.
He knows what sells best on the
market.

21. Q: I am a developer.
Can I just start building?
A: No. You need
a development
environment.
Ask Adam Admin to
build it for you.

22. Q: What is the
Definition of Done?
A:
1. One LEGO Animal.
2. One number label.
3. One candy.
4. Package is closed.

23. Q: This PBI is Done.
Can we deploy it?
A: Not so fast!
Robert Release
needs to
package it for
deployment.
Sara needs to run
a security scan.

24. A: Benjamin Business
will pay for products
delivered and accepted
in production.
Q: How will
we get
paid?

25. Sprint 1: Cyclical Value Delivery
With Scrum
• Dev and Ops are
separate teams
• Sys Admin controls
release schedule
• Security tests are at
the end of the Sprint

26. What Have You Observed in
Sprint One?

27. Ready for
DevOps?
Where Do You

28. The Three Ways

29. Optimize Your Flow

30. Typical Bottlenecks in DevOps
Transformation
1. Environment creation.
2. Large batch size code merges.
3. Code deployment.
4. Test setup and run.
5. Overly tight architecture.
6. People unwilling to change.

31. Fix your
worst
bottleneck
first!
“Any improvements made anywhere
besides the bottleneck are an illusion.”
Gene Kim, The Phoenix Project: A Novel About IT, DevOps, and Helping Your Business Win

32. Dev Ops
Invite Operations Into Your Teams

33. Sprint 2: First Steps Towards
DevOps
• Invite Operations into
your teams.
• Build T-shaped skills
with cross-training.
• Start automating
environment creation.

34. How Was
the
Sprint
Two
For Your
Team?

35. Split Work Into Smaller Batches

36. Simplify and Automate Your
Deployments

37. Sprint 3: Continuous Value
Delivery
• Enable better flow with
reduced batch sizes.
• Accelerate the feedback
loop with simplified
deployment.
• Anyone can create an
environment!

39. Pursue Further
Feedback Loop
Amplification
1. Telemetry – implement, collect, make visible
to all.
2. On-call rotation – involve developers and
architects.
3. Have developers initially self-manage their
instance of production servers.

40. Experiment and
Practice to Reach Mastery
1. Inject failure to test resilience.
2. Blameless postmortems.
3. Share team learning with the rest
of the organization.

41. Share Your Aha!
Moments

42. Recommended Reading:

43. Level Up+
Thank you

44. Links and Credits
1. https://www.getchef.com/blog/2010/07/16/what-devops-
means-to-me/
2. https://puppet.com/resources/whitepaper/state-of-devops-
report
3. https://blog.newrelic.com/2014/05/16/devops-name/
4. http://continuousdelivery.com
5. https://pixabay.com/
6. http://www.shutterstock.com/pic-151104653/stock-photo-
crazy-scientist-young-boy-performing-
experiments.html?src=Vq0HbZwnUpigKG9b1ITx_A-1-1
7. http://vectorcharacters.net/