DevOps Introduction and Purpose
What DevOps is
DevOps is a cultural and professional movement that combines people, process and technology so an organisation can shorten the time between committing a change and running it safely in production, while improving quality and reliability. It emerged because Development and Operations had conflicting incentives: Dev optimised for change, Ops optimised for stability. The result was long handoffs, late discovery of problems and blame when a release failed. The term was popularised around 2009, alongside early "10+ deploys per day" talks that showed high performance and stability were compatible.
Concepts a candidate must know
- CALMS: Culture, Automation, Lean, Measurement, Sharing - both a maturity lens and a test of whether an initiative is genuinely DevOps.
- The Three Ways: flow of work from Dev to Ops; amplified feedback loops; a culture of continual experimentation and learning.
- Definition traps: DevOps is not a team, a role, a job title or a product. Cross-functional teams own the product from code to customer.
- Purpose and benefits: faster time to market, more frequent releases, lower change failure rate, faster recovery, better staff and customer experience.
- Relationship to Agile: Agile focused mainly on development and planning; DevOps extends the same thinking across the whole value stream, including operations and production.
Traps that appear in questions
"The company formed a DevOps team to handle all deployments" sounds plausible but re-creates the silo it was meant to remove. "We bought a DevOps tool, so we do DevOps" confuses means with outcome. "DevOps removes the need for operations skills" is false - those skills are embedded, not deleted. "DevOps only suits web startups" is also false; regulated and traditional enterprises adopt it with appropriate controls.
Rule of thumb
If an answer defines DevOps primarily as a tool, a job title or a new team, it is almost certainly the distractor.