The document discusses the transformation of applying DevOps and Agile principles at scale within organizations, emphasizing the need for continuous improvement and effective planning frameworks. It critiques the waterfall development model for its rigidity and explores Agile development's frequent integrations and short planning cycles. Key focus areas include enhancing feedback quality, optimizing deployment processes, and cultivating a collaborative culture among development and operations teams.

1. Leading the Transformation
“Applying DevOps and Agile Principles at Scale”
Gary Gruver

3. Requirements Scheduling Development
Integration &
Qualification
Waterfall Development Model
Resources
Waterfall Approach:
Do enough up front planning
to lock in all three corners
ScheduleScope
Waterfall Reality:
Discoveries during
development and difficulties
with integration/qualification
results in frequent and
costly schedule slips

4. Agile Development Model
Plan
Qual Dev
• Fully qualified code drops on a fixed schedule
• Frequent small integrations
• Short planning and development cycles
• Delivering to a well prioritized product backlog
Plan
Qual Dev
Plan
Qual Dev
Plan
Qual Dev
Drops of Working
Complete Code on
A Fixed Interval

5. Scrum Agile≠

6. Water Scrum Fall

7. Leading the Transformation
Enterprise Level
Continuous
Improvement

8. Planning & Prioritized
Backlog
Leading the Transformation
Enterprise Level
Continuous
Improvement

9. Planning & Prioritized
Backlog
Applying DevOps
Principles at Scale
Leading the Transformation
Enterprise Level
Continuous
Improvement

10. Business Objectives (Don’t “Do Agile”)
Define
your value
proposition
Understand your
cost & cycle-time
drivers

11. Business Objectives (Don’t “Do Agile”)
Define
your value
proposition
Understand your
cost & cycle-time
drivers
Either automate, eliminate, or engineer out the
drivers that aren’t key to the value prop

12. Planning & Prioritized
Backlog
Applying DevOps
Principles at Scale
Leading the Transformation
Enterprise Level
Continuous
Improvement

13. Enterprise Level Continuous Improvement
Mini-milestone
Objectives
Cascading Objectives
to Track Progress
ConversationsLearnings
Agile Adjustments

14. Planning & Prioritized
Backlog
Applying DevOps
Principles at Scale
Leading the Transformation
Enterprise Level
Continuous
Improvement

15. Long Term Predictability for SW Schedules
100%
Accuracy
Planning Investment

16. Planning & Prioritized
Backlog
Applying DevOps
Principles at Scale
Leading the Transformation
Enterprise Level
Continuous
Improvement

17. Business Objectives for Applying DevOps at Scale
Increase the quality and frequency of feedback
Reduce the time and resources between release branch & production
Improve deployment repeatability/env. stability
Testing in an Operational like environment as close to dev. as possible

18. Finding the offending code

19. Finding the offending code

20. Finding the offending code
What Code?
When? Are you
sure it wasn’t Bob?

21. Developing on Trunk

22. Automated system test architecture
• Component based approach to the automated test architecture
Data Magic
Navigation
Page Objects

23. Scripting Environments - Variances
Dev/QA PRE-PROD PERFORMANCE PRODUCTION
Common Script
Environment descriptors

24. Scripting Environments - Variances
Dev/QA PRE-PROD PERFORMANCE PRODUCTION
Common Script Common Script
Environment descriptors

25. Scripting Environments - Variances
Dev/QA PRE-PROD PERFORMANCE PRODUCTION
Common Script Common Script Common Script
Environment descriptors

26. Scripting Environments - Variances
Dev/QA PRE-PROD PERFORMANCE PRODUCTION
Common Script Common Script Common ScriptCommon Script
Environment descriptors

32. Auto-revert/Gated Commits

33. Gating Commits

34. Building Up
the Enterprise
System

36. Shifting the Culture
• Getting Leaders across the organization to engage in leading the
transformation with a common set of priorities
• Getting developers to ensure every check-in to trunk is stable in a
production like environment as job #1.
• Getting development and operation teams using common tools and
environments so they share common objectives.
• Getting the entire organization to agree that the definition of done at the
release branch.
• Embrace the unique characteristics of software and design a planning
process that takes advantage of its flexibility.

38. Leading the Transformation
“Applying DevOps and Agile Principles at Scale”
E-mail: gbgruver@gmail.com
Blog: largescaleagile.com
Twitter: @GRUVERGary
garygruver@sendyourslides.com subject:Transformation