Chapter 1 - DevOps History
(6883 words)
1. The limits of agility in application development
1.1 The contributions of Lean
1.2 The Agile revolution
1.2.1 The search for a new engineering
1.2.2 The end of the V-cycle
1.2.3 The path of change
1.3 An unfinished construction
2. Specialization and separation of responsibilities in ISDs
2.1 Specialization
2.2 Siloing
2.3 Silos vs Agile: a complicated marriage
3. the infrastructure automation paradigm
3.1 The meeting
3.2 Technology as a common denominator
3.3 Change through practice
4. The contribution of "continuous delivery
4.1 Continuous integration
4.2 Continuous delivery
Chapter 2 - The wall of confusion
(10144 words)
1.1 A great project
1.2 Real life
1.3 Product reception and technical choices
2. An insurmountable technical debt and a weakened product
2.1 The anxiety of change
2.2 A slow life cycle
3. the wall of confusion: change versus stability
3.1 Internal tensions
3.2 The wall of confusion
3.3 The consequences
4. the challenges that await you
5. Expected benefits of devops
5.1 Innovate
5.2 Focusing efforts and costs on value
5.3 Reducing the lead-time from idea to market
5.4 Being resilient and anti-fragile
6 The three ways of devops
Chapter 3 - DevOps principles
(4654 words)
1. focus on the customer's needs
1.1 The Agile approach
1.2. Devops is an Agile practice centered on the customer need
2. build with awareness of the objective
2.1 The problem of intermediate objectives
2.2 The difficult reconstruction of the global objective
3. End-to-end collective responsibility
4. Cross-functional and autonomous teams
4.1 The cross-functional team
4.2 The need for autonomy and decision making
5. Continuous improvement
5.1 A systemic tool at the heart of the team
5.2 The key principles of continuous improvement in Devops
5.2.1 If it hurts, do it more often
5.2.2 Failing fast
6. Automate everything that can be automated
Chapter 4 - Agile culture and DevOps
(13371 words)
1. A culture of communication rather than contract
1.1 The rules of the contract
1.2 The impact of the contract in the Agile world
1.3 How to evolve supplier contract management in a Devops organization
1.3.1 Value at the center of the Agile contract
1.3.2 The different phases of the Agile contract
1.4. What are the impacts for devops
1.5. What Impacts for Procurement and Legal Services
2. A culture of results rather than process
2.1 For what result?
2.2 How to manage the continuity of knowledge and skills10
2.2.1 Adapting the life cycle: from project to product
2.2.2 Use existing tools to document
2.3 How to manage performance
2.3.1 The trap of performance indicators
2.3.2 Agile and Devops design of success measurement
2.3.3 The contribution of OKRs
3. A learning organization rather than a blame culture
3.1 Conditions that promote learning
3.1.1 Trust
3.1.2 Avoidance
3.1.3 Building on failure
4. Managerial posture
4.1.1 Management by control
4.1.2 Foster leadership over authoritarianism.
4.1.3 The myth of 100% productivity
5. impact on HR strategies
5.1 Changing recruitment
5.2 Evaluation: simplifying and desecralize
5.3 The importance of training
5.4 The human adventure
Chapter 5 - DevOps organizational model
(8962 words)
1. What are the organizational issues?
1.1 The understanding of the IT organization by the business
1.2 The importance of simplicity
1.3 The problem of the cost of interactions
2. The Devops organization
2.1 A problem of scale
2.1.1 The small scale
2.1.2 The large scale
2.2 The Spotify experience
2.2.1 The history of a scale-up
2.2.2 The organization
2.2.3 What about Devops in the model?
2.3 The SAFe framework
2.3.1 A top-down alignment model
2.3.2 Train and release management
2.3.3 Devops in SAFe
2.4 The fundamentals of an adaptive model
3. The limits of the system
Chapter 6 - Configuration management
(10917 words)
1. The basis: versioning everything you produce
1.1. Why versioning
1.2. Versioning for better automation
1.3. Versioning for collaboration
1.4 The impact of deployment models
2. Versioning strategies
2.1 Basic principles
2.2 The different strategies
2.2.1 Feature branching
2.2.2 Continuous integration
2.2.3 Production versions
2.3 The improvement trajectory
2.4 Organizational benefits
3. Manage the configuration of the components
3.1 The libraries
3.1.1 The execution environments
3.1.2 External function libraries
3.2 The components
3.2.1 Highlighting the dependency graph
3.2.2 Identify anomalies
3.3 Managing artifacts
3.3.1 Create an artifact repository
3.3.2 Artifact repository in the integration chain
Chapter 7 - CI/CD principles
(7057 words)
1. The application life cycle
1.1 How to define the life cycle?
1.2 Managing value
1.3 Managing the life cycle
2. Integrate and deploy continuously
2.1 Objectives
2.2. Principles of continuous integration
2.3. Principles of continuous deployment
2.3.1 Continuous delivery
2.3.2 Continuous deployment
3. Deployment strategies
3.1 Initiate the first deployments
3.1.1. Old school story ...
3.1.2 The lean-devops way
3.2 The principles of continuous deployment
3.3 Blue/green deployment
3.4 The Canary deployment
3.5 A/B testing
3.6 The darks launch
Chapter 8 - Automation and Lean IT
(7840 words)
1. Automate everything that can be automated
2. Rollback
3. Infrastructure as code
3.1 Creating system resources
3.1.1 Automatic provisioning
3.1.2 The life cycle of a system resource
3.1.3. Create and maintain the system
3.2 The idempotency
3.2.1. Definition
3.2.2 What does this solve?
3.2.3 How does it apply?
3.2.4 What is the consequence on automation?
4. On-demand environments
4.1. Before Devops
4.2. With Devops
4.3 The impact on costs, the finops
5. The relationship with the cloud
5.1 The principles of automation in the cloud
5.2 Containerization and orchestration
5.3 PaaS (Platform as a service)
Chapter 9 - Measure and Improve
(6057 words)
1. Observability
1.1 Monitoring
1.2 Observability
2 Devops indicators
2.1 Lead Time
2.1.1 Definition and limits
2.1.2 The timeframe for the implementation of anomaly corrections
2.1.3 The timeframe for the implementation of user-stories
2.1.4 The timeframe for implementing the functionalities
2.1.5 Time to market for an idea
2.2 Frequency of deployment
2.3 The failure rate of change
2.4 Mean Time To Recovery (MTTR)
