Score 100% on the quiz to continue
What DevOps is
Two teams with opposite goals, work thrown over the wall, and DevOps as one team sharing responsibility for the result.
Before talking about pipelines, let's look at the problem DevOps was born to solve. It is a people problem first, and a tooling problem only second.
Two teams with opposite goals ⚖️
For a long time, most companies split software work between two teams:
- Development wrote the code. Developers were rewarded for change: new features, delivered fast.
- Operations ran the code in production: servers, networks, databases, deploys, and the pager at 3 a.m. Operations was rewarded for stability: nothing breaking, ever.
Look at those two goals side by side. Every change is a risk to stability, so the two teams were measured in ways that pulled against each other. Developers wanted to ship more often; operations wanted to ship less often, and with more checks. Both were doing their jobs well.
Thrown over the wall 🧱
Between the two teams there was a wall. Development finished a release, packaged it, and "threw it over the wall" to operations, often with a document of instructions nobody had tested. Operations tried to install it on servers that were configured differently from the developers' machines. Something failed.
You have probably heard the punchline already:
"It works on my machine."
That sentence describes a release night in those companies: a long evening (or weekend) where a large batch of changes, built over weeks or months, went to production all at once. When something broke, nobody knew which of the hundred changes caused it, and each team pointed at the other.
What DevOps is 🤝
The name says it: DevOps joins Development and Operations in a single word. It was coined around 2009 by Patrick Debois, who organized the first DevOpsDays conference, in Ghent, Belgium.
DevOps is the answer: development and operations stop being two sides of a wall and become one team sharing responsibility for the result, from the idea to the user. In practice, that means:
- The people who build a feature also care about how it runs in production
- The people who run production take part early, when the feature is still being designed
- Changes are small and frequent, so each one is easy to understand, test, and undo
- Everything that can be automated (building, testing, deploying) is automated, so it happens the same way every time
- The team learns from production, from failures, and from its own process, and keeps improving
What DevOps is not 🚫
- Not a tool. GitHub Actions, Jenkins, Docker, and Kubernetes are tools a DevOps team may use. Adopting them changes nothing if the teams still throw work over a wall.
- Not a job title. A "DevOps engineer" can help a team automate, but one person cannot hold a culture for everyone else.
- Not a third team. A separate "DevOps team" sitting between development and operations is just a new wall, with a new team behind it.
What this means for a tester 🧪
The wall had a third side, and it was usually QA.
In many of those companies, testing was a phase that happened after development and before operations: developers handed a build to testers, testers handed a report back, and eventually the build went over the wall. Testers were rewarded for finding bugs late, which is the most expensive time to find them, and were often blamed when one escaped.
DevOps changes the tester's place too. When quality is a shared responsibility, testing stops being a phase at the end and becomes something that happens all along the way: reviewing an idea before it is built, checking each small change automatically, and watching what happens in production. The rest of this course shows each of those places.
Suggested content 📚
- Software Testing Fundamentals, for the test levels and types this course places along a pipeline
- The DevOps Handbook, by Gene Kim, Jez Humble, Patrick Debois, John Willis, and Nicole Forsgren
Show the world what you learned 🌎
To show your professional network what you have learned in this lesson, post the following on LinkedIn.
I am taking the "DevOps for Testers" course by @Walmyr Lima e Silva Filho at the @Talking About Testing School, where I learned the problem DevOps was born to solve: two teams with opposite goals, work thrown over a wall, and release nights full of "it works on my machine". DevOps is a culture of shared responsibility, not a tool or a job title, and testing belongs all along the way, not at the end. #TalkingAboutTesting #TATSchool #DevOpsForTesters #DevOps #QualityAssurance
👨🏫 Remember to tag me in your post. Here is my LinkedIn profile.
Quiz
Before DevOps, why did development and operations so often pull against each other?
Score 100% on the quiz to continue