DevOps Adoption Strategies

DevOps is a set of best practices enabling operations and development teams to work together to produce higher-quality work and, among other things, quicker releases. This book helps you to understand the fundamentals needed to get started with DevOps, and prepares you to start deploying technical tools confidently.

You will start by learning the key steps for implementing successful DevOps transformations. The book will help you to understand how aspects of culture, people, and process are all connected, and that without any one of these elements DevOps is unlikely to be successful. As you make progress, you will discover how to measure and quantify the success of DevOps in your organization, along with exploring the pros and cons of the main tooling involved in DevOps. In the concluding chapters, you will learn about the latest trends in DevOps and find out how the tooling changes when you work with these specialties.

By the end of this DevOps book, you will have gained a clear understanding of the connection between culture, people, and processes within DevOps, and learned why all three are critically important.

• Section 1: Principles of DevOps and Agile
1. Introducing DevOps and Agile
• Exploring the goals of DevOps
• Deployment frequency
• Faster time to market
• Lower failure rates
• Shorter lead times
• Improved recovery time
• Values associated with DevOps
• Challenges solved by DevOps
• Addressing these challenges
• Phases of DevOps maturity
• Waterfall
• Continuous integration
• Continuous delivery
• Continuous deployment
• How does Agile play a part in DevOps?
• The Agile manifesto
• Do Agile and DevOps work together?
• Agile is more than Scrum
• Dealing with unplanned work
• What is Scrum?
• Kanban
• Kanplan
• Mixing methodologies within organisations
• Scaling Agile teams
• Summary
2. Business Benefits, Team Topologies, and Pitfalls of DevOps
• Key business benefits of DevOps
• CX
• Business growth
• Cost savings
• Boost in productivity
• Improved employee retention
• Better quality products
• Higher customer satisfaction
• Improved operational and process efficiency
• Transformation topologies
• Development and operations collaboration
• Shared operations
• DevOps as a Service
• DevOps advocacy
• SRE
• Container driven
• Transformation anti-patterns
• Development and operations silos
• DevOps team silo
• Development does not need operations
• DevOps as a tooling team
• Glorified SysAdmin
• Operations embedded in development
• Avoiding failed transformation projects
• Rooting DevOps initiatives within customer values
• Management of organizational change
• Failing to collaborate
• Management of expectations in terms of DevOps initiatives
• Decoding failed DevOps transformation
• Summary
• Questions
3. Measuring the Success of DevOps
• Common metrics used to measure success
• Common velocity metrics
• Common quality metrics
• Common stability metrics
• Designing metrics for your team
• Scenario 1: Small organization with a dedicated DevOps team
• Scenario 2: Medium organization with advocacy team
• Scenario 3: Large organization with numerous DevOps teams
• Scenario 4: Small organization with outsourced DevOps team
• Creating rollups at an organizational level
• Reporting when multiple teams work on one product
• Reporting when multiple teams work on multiple products
• Creating goals that are S.M.A.R.T
• Summary
• Section 2: Developing and Building a Successful DevOps Culture
4. Building a DevOps Culture and Breaking Down Silos
• What is a DevOps culture?
• Roles and responsibilities workshop
• Rules of engagement
• Retrospectives
• Why is culture important?
• Increasing transparency
• Better communication
• Collaboration across teams
• Maintaining a strong culture
• Starters and leavers
• Pushing too hard for success
• Lack of innovation
• Cultural differences
• Lack of buy-in
• Breaking down silos in your organization
• Creating one vision for team collaboration
• Working toward common goals with collaboration tools
• Educating together, working together, and training together
• Communicating often
• Evaluating team compensation
• Summary
• Questions
5. Avoiding Cultural Anti-Patterns in DevOps
• Organizational alignment
• Resistance to change
• Understanding the roles of organizational change
• Organizational change process steps
• Overcoming resistance
• Breakdown in communication
• Difficulty scaling up
• Start with small teams
• Encouraging skill development
• Prioritizing culture
• Continuous feedback
• Automation
• Excessively focusing on tooling
• How much automation is too much?
• Legacy infrastructure and systems
• Legacy modernization
• Summary
• Questions
• Section 3: Driving Change and Maturing Your Processes
6. Driving Process Change with Value Stream Maps
• Understanding value stream mapping
• Going beyond DevOps for process improvement
• Taking a look at value stream mapping diagrams
• How does value stream mapping help?
• Challenges of value stream mapping
• Use cases of value stream mapping
• Identifying end reducing waste
• Analyzing differences between process maps and value stream maps
• Which should I use?
• Explaining an example value stream map
• Creating a value stream map
• Current state value stream map
• Future state value stream map
• Summary
• Questions
7. Delivering Process Change in Your Organization
• Eight steps for effective change
• Identifying what will be improved
• Presenting a business case to stakeholders
• Planning for change
• Identifying resources and data for evaluation
• Communicating
• Evaluating resistance, dependencies, and risk
• Celebrating success
• Continuously improving
• Models for business change
• Kotter's change management model
• Rogers' technology adaption curve
• The ADKAR model
• The EASIER model
• People effects of process change
• Direct impact
• Indirect impact
• The common challenges of process change
• Summary
• Questions
8. Continuous Improvement of Processes
• What is continuous improvement and feedback?
• Building a continuous improvement culture
• Understanding and implementing Kaizen principles
• Building a continuous feedback culture
• Techniques for continuous improvement and feedback
• Continuous improvement processes
• Additional continuous improvement techniques
• The continuous feedback process
• Additional continuous feedback techniques
• Iterating changes to processes
• Iterative design processes
• Using iterative design
• Benefits of iterative design
• Keeping pace with change
• Effective communication
• Knowledge transfer
• Access to subject matter experts
• Summary
• Questions
• Section 4: Implementing and Deploying DevOps Tools
9. Understanding the Technical Stack for DevOps
• What are the families of DevOps tools?
• Collaborating
• Building
• Testing
• Deploying
• Running
• How does tooling help the adoption of DevOps?
• Choosing tools that facilitate collaboration
• Using tools that enhance communication
• Lean toward tools with APIs
• Always encouraging learning
• Avoiding environment-specific tools
• Understanding the benefits of DevOps tooling
• Increasing code and deployment velocity
• Reduction of time to market for new products and features
• Decrease in the failure rate of new releases
• Improving the mean time to resolution
• Improvement in reliability metrics
• Eliminating high levels of work in progress and technical debt
• Understanding the obstacles of DevOps tooling
• Lack of definition of DevOps outcomes
• Inadequate knowledge of tooling
• Evaluation of tools
• The volume of tools available on the market
• Lack of tool integration
• Summary
• Questions
10. Developing a Strategy for Implementing Tooling
• Understanding architectural and security requirements
• Why is enterprise architecture important?
• Why is information security important?
• Understanding architectural requirements
• Developing training plans to help your team
• Why are training plans important?
• How to develop training plans for your teams
• Defining owners and processes for tooling
• Identifying the owners of tools in your organization
• Mapping processes to tools
• Making tooling part of process improvement
• Summary
• Questions
11. Keeping Up with Key DevOps Trends
• What is XOps?
• Where did XOps begin?
• Understanding the XOps landscape
• Approach to XOps
• Understanding the DataOps ecosystem
• Understanding processes involved in DataOps
• Understanding tools involved in DataOps
• Understanding the DevSecOps ecosystem
• Understanding processes involved in DevSecOps
• Understanding tools involved in DevSecOps
• Understanding the GitOps ecosystem
• Understanding processes involved in GitOps
• Understanding tools involved in GitOps
• Summary
• Questions
12. Implementing DevOps in a Real-World Organization
• Understanding why organizations move to DevOps
• Technical benefits
• Cultural benefits
• Balancing stability against new features
• Increased effectiveness
• Defining our fictional organization
• Current operating model
• Challenges that exist within the current model
• Goals for the future
• Walk-through of DevOps transformation
• Having initial planning workshops
• Establishing a DevOps Center of Excellence
• Setting up governance of the transformation
• Establishing an intake process
• Identifying and initiating pilots
• Assessment of current capabilities
• Performing transformation exercises
• Scaling out the DevOps transformation
• Summary
• Why subscribe?
• Other Books You May Enjoy

This has to be one of the best DevOps books for grown-ups I have ever read.

Succint, explaining history of XOps, business impact, change and implementation processes, variants, etc, etc.

Recommended reading if you want to look into DevOps without the hype or preaching.