Ariadne needs a new database server to support her new search feature. This should only take a few minutes but it’s stuck in the Operations team’s backlog! She might have to wait months for this simple task. What’s going on?! Ariadne’s coworker Jenna suggests trying out a new team strategy called DevOps. Ariadne is not familiar with this term — what’s DevOps?
DevOps is a culture that shifts the way that Development and Operations team members work together. DevOps culture aims to foster trust, collaboration, problem resolution, and continuous improvement across the entire team. So how can Ariadne’s team adopt a DevOps culture to increase collaboration and reduce barriers between these departments?
Teams use a variety of practices and tools in order to foster a DevOps culture. You may have even heard of some of these practices, such as automation or blameless retrospectives. Your team may already use some of these tools, such as version control systems. On their own, these practices and tools can certainly make improvements. When used within a DevOps culture, a team can be transformed.
This lesson will start by looking at traditional team culture before introducing the core pillars of a DevOps culture. We’ll cover:
- Development versus Operations teams
- Dev+Ops: Shared Responsibilities and Roles
- Systems-Level Thinking
- Learning From Failure
- Feedback Loops
Ariadne’s team struggled because of the separation between her Development and Operations teams. In the next exercise, we’ll take a look at the responsibilities of each of these teams in a traditional company structure like Ariadne’s. After that, we’ll learn how teams that embrace DevOps culture share those same responsibilities.