BCS Foundation Level Certificate in DevOps Exam

1. Introducing DevOps

This module provides the historical context and the fundamental "why" behind the movement.

Traditional IT Challenges: Understanding the "Wall of Confusion" between development and operations and how silos lead to bottlenecks.

History and Key Events: Origins of the DevOps movement (e.g., Velocity 2009, Patrick Debois, and the Agile connection).

Definition of DevOps: What it is—and just as importantly, what it is not (e.g., not just a job title or a tool).

The Business Case: Justifying transformation through improved stability, speed, and quality.

2. Core Principles: The Three Ways

Based on the seminal work in The Phoenix Project, these principles form the backbone of the exam.

The First Way (Flow): Systems thinking and optimizing the global workflow from left (Dev) to right (Ops).

The Second Way (Feedback): Creating and amplifying right-to-left feedback loops to prevent problems from recurring.

The Third Way (Continual Learning): Fostering a culture of experimentation, taking risks, and learning from failure.

3. Cultural Aspects

Culture is considered the most critical (and difficult) component of DevOps.

Models of Organizational Culture: Deep dive into Westrum’s Typology of Organizational Cultures (Pathological, Bureaucratic, Generative).

Team Dynamics: Understanding Tuckman’s Stages of Group Development (Forming, Storming, Norming, Performing).

Motivation: Exploring Herzberg’s Two-Factor Theory (Hygiene factors vs. Motivators).

The CALMS Model: Culture, Automation, Lean, Measurement, and Sharing.

4. Automation

This section covers the technical pipeline and the removal of manual toil.

Deployment Pipeline: The concept of the "Continuous Delivery" pipeline.

Continuous Integration (CI): Merging code frequently and automated builds.

Continuous Delivery vs. Deployment: The difference between being "ready to deploy" and "automatically deployed."

Infrastructure as Code (IaC): Managing environments through machine-readable definition files rather than manual configuration.

Testing Pyramids: The importance of automated unit, integration, and UI testing.

5. Lean Practices

Applying Lean manufacturing principles to software delivery.

The 8 Types of Waste (Muda): Identifying non-value-add activities like defects, overproduction, and waiting.

Theory of Constraints (TOC): Identifying the single weakest link in a process (the bottleneck) and managing it.

Work in Progress (WIP): Understanding why high WIP kills productivity and how to limit it.

Visualizing Work: Using Kanban boards to create transparency.

6. Measurement and Metrics

Focuses on measuring the right things to drive the right behaviors.

Alignment: Ensuring IT goals align with business outcomes.

DORA Metrics: Understanding the four key industry-standard metrics:

Deployment Frequency.

Lead Time for Changes.

Change Failure Rate.

Time to Restore Service.

Lead Time vs. Cycle Time: Defining the start and end points of value delivery.

7. Sharing and Collaboration

Breaking down silos through communication.

Communication Tools: ChatOps and collaborative platforms.

Knowledge Management: The importance of Wikis, "Lunch and Learns," and Communities of Practice (CoPs).

Shadowing: Learning by observing different roles to build empathy.

8. Common DevOps Roles

Understanding how traditional roles evolve in a DevOps environment.

T-Shaped Individuals: Generalizing specialists who have deep knowledge in one area but broad skills in others.

Key Roles: The DevOps Evangelist, Automation Architect, Cloud Infrastructure Engineer, Site Reliability Engineer (SRE), and the Product Owner.

9. Methods and Frameworks

How DevOps interacts with other popular industry frameworks.

Agile: The relationship between the Agile Manifesto and DevOps.

ITSM/ITIL: How DevOps and IT Service Management can coexist and complement each other.

Scrum and Kanban: Using these frameworks to manage flow within DevOps teams.