To realize the enormous benefits possible with DevOps Continuous Delivery requires a strategic approach and adherence to best practices for leadership, culture, organization, process and technologies. Preferred product and systems architectures are described in this deck. The slide deck is a high level summary of an one day course being delivered at the DevOps India Summit in Banglaru August 30, 2018.

1. Engineering Continuous Delivery Architectures
Marc Hornbeek - DevOps Principal Consultant

2. Marc Hornbeek, DevOps Principal Consultant
“DevOps-the-gray”
• 41 years IT experience with emphasis on leadership of
automation, architecture, design, development and
management of high-performance projects for DevOps,
software systems, QA, networks and testing labs
• 2016 IEEE Outstanding Engineer of the Year – Western
USA
• Thought leader, speaker, blogger, author, mentor, advisor,
teacher
• Techbeacon 2018 - #30 of DevOps 100: Top leaders,
practitioners, experts
• Employers: Confinity Consulting, Trace3, Bell-Northern
Research, Tekelec, ECI Telecom, GSI Lumonics, Vpacket,
EdenTree Tech., and Spirent Com.
• Education: B.Sc. Engineering, Executive MBA, CEs, Certs
• 50+ DevOps transformations: Enterprise, manufacturers,
service providers

3. 3
DevOps
Certification
Programs

4. 4
Table of
Contents
• Architecture considerations
• DevOps assessment
• Select and architect a model application
• DevOps enterprise adoption programs
• Road-mapping DevOps journeys
• Using ROI to justify DevOps transformations
• Benefits expected
• Learning more…

5. 5
CI/CD
pipeline
continuous
flow with CT When the DevOps continuous delivery pipeline is
architected correctly you will realize increased, faster
software release delivery, improved quality, and
improved customer satisfaction.

6. 6
Architecture
Considerations
for DevOps
Architecture
limits DevOps
performance
DevOps-Ready
Application
• Modular 12-factor
apps
• Elastic
• Cloud native
• Service oriented
• Microservices
• Containers
• Testability
• Observability
DevOps-Ready
Toolchain
• Self service , APIs
• Elastic
• Orchestration
• Automation
• Scalable
• Containers
• Multi-pipeline
• Observability

7. 7
Select a model
application for
DevOps
Why?
1. DevOps
experimentation,
implementation and
improvements
2. Demonstrate return on
investment for DevOps
projects
3. Reference that other
application teams can
learn from and apply to
their applications
Selection
considerations
1. Lead time
2. Leadership
3. Culture
4. Application
architecture
5. Product Team
size
6. Duration
7. Impact/Risk
8. Frequent changes
9. Tools
10.Effort per release

8. 8
DevOps Assessment
Recommendations &
high level roadmap
2017 State of DevOps Market Segmentation Report
• Two-thirds cited deployment automation as a starting point for DevOps
• 62 percent cited version control
• 59 percent cited continuous integration
• 57 percent cited infrastructure automation
Align terms, goals,
approach, success
Surveys
Vision
Practices
Value
Stream
Interviews
Workshops

9. 9
27 Critical
Success
Factors
Strategy for
navigating complexity
Nine Disciplines
1. Collaborative
Leadership
2. Collaborative Culture
3. Design for DevOps
4. Continuous
Integration
5. Continuous Testing
6. Elastic Infrastructures
7. Continuous
Monitoring
8. Continuous Security
9. Continuous
Delivery/Deployment
Three
Dimensions
1. People
2. Process
3. Technology
DevOps Three Ways
1st Way: Continuous Flow
2nd Way: Continuous Feedback
3rd Way: Continuous Improvement
X

10. 10
DevOps Adoption Program Blueprint
Leadership / Culture Initiative
Model DevOps project
Additional DevOps projects
• DevOps Adoption Goals
• DevOps leadership
training
• Organization preparation
• Model project selection
• Investment (team &
tools)
• Architecture team
• Monitoring and
incentives
• Team and organization
• Training (CI/CD practices)
• Goals, Assessment, Value Stream
• Tool chain with ARA backbone
• Automate CI and QA automation
• Automate CD , containers, G/B, A/B
• DevSecOps
• KPIs and monitoring tools
• Site Reliability Engineering
• Optimize (Kaizen)
Additional DevOps projects
Additional DevOps projects
• App Selection
• Self contained product teams
(squads, tribes)
• Proactive sharing or practices
(Yokoten)
• Info sharing (Chapters and Guilds)
SCALE !
Systematic, measured,
maturity progression
POC MVP
2nd
Way
1st
Way
3rd
Way

11. 11
Benefits Expected = Return on Investment
https://techbeacon.com/devops-roi-how-measure-guide
https://devops.com/the-roi-of-enterprise-devops/

12. 12www.xellentro.com

13. 13
https://www.xellentro.com/devops-india-summit-2018/