EXIN DevOps Foundation

1. DevOps Basics

1.1 DevOps Origins

• Describe the historical developments from Waterfall to Scrum to Agile.
• Describe the developments in virtualization and cloud computing that enable DevOps.
• Explain how DevOps developed from a historical perspective.

1.2 Definition of DevOps

• Outline how DevOps is an expansion of Lean and Agile thinking.
• Explain that DevOps requires value stream thinking.
• Clarify how DevOps can yield a greater return on IT than other practices.

1.3 Reasons for Using DevOps

• Identify decreasing time to market as a reason for using DevOps.
• Identify reducing technical debt as a reason for using DevOps.
• Identify eliminating fragility as a reason for using DevOps.

1.4 Misconceptions About DevOps

• Clarify that DevOps is not a part of Agile.
• Clarify that DevOps is more than tools and automation.
• Clarify that DevOps is not a new profession.

2. DevOps Principles

2.1 Value Stream

• Define the concept of a value stream.
• Explain the concept of a value stream map (VSM).
• Clarify how a value stream map (VSM) may help optimize processes in the business.
• Explain why value stream thinking is the core of DevOps.

2.2 Deployment Pipeline

• Define the concept of a deployment pipeline.
• Identify the challenges when implementing a deployment pipeline.

2.3 Version Control

• Define the concept of version control.
• Explain why version control is important.

2.4 Configuration Management

• Define the concept of configuration management.
• Explain why configuration management is important for DevOps.

2.5 Definition of Done (DoD)

• Explain why a clear definition of done (DoD) is important for working with a DevOps mindset.

3. DevOps Key Practices

3.1 Difference with Traditional Practices

• Clarify how DevOps facilitates more frequent releases.
• Clarify how DevOps focuses more on adding value to the business.
• Explain that DevOps requires automation.
• Clarify how DevOps deals with solving incidents and defects differently.
• Clarify how DevOps needs continuous improvement.

3.2 DevOps Practices

• Outline the importance of a diverse team.
• Outline the importance of visualizing work.
• Outline why work in progress (WIP) and batch sizes should be limited.
• List how DevOps incorporates operational requirements into Development.
• Explain the importance of supporting innovation.
• Identify ways to deal with bottlenecks.

4. Practical Applications of DevOps

4.1 Applicability

• Characterize situations in which DevOps is feasible.
• Identify conditions that make adoption of DevOps interesting for the business.

4.2 Limitations

• Identify a lack of readiness to adopt DevOps.
• Characterize monolithic IT infrastructure and architecture as a limitation for adopting DevOps.

4.3 Using Commercial Off-the-Shelf Software (COTS)

• Clarify the risk of COTS in strategic business lines.
• Identify solutions for working with COTS when there is no other option.

4.4 Evolving Architecture and Organizational Models

• Identify the difficulties a rigid IT department poses on implementing DevOps.
• Characterize the need for a flexible mindset to change and innovation.

4.5 Iterative Progression

• Recall that DevOps may start small and can be built up from there.
• Recall that DevOps is a way of thinking, which may start anywhere in the organization.