Agile and DevOps: Friends or Foes? Understanding Their Relationship and Practices
This article explores the nuanced relationship between Agile and DevOps, clarifying common misconceptions, detailing how Scrum and continuous delivery intersect, and presenting the three‑layer DevOps model that helps teams integrate cultural, technical, and delivery practices for better collaboration and value delivery.
Agile and DevOps: Friends or Foes? The article begins by questioning whether Agile and DevOps are competing philosophies or complementary partners, noting that both extend beyond software teams and often get confused due to overlapping jargon.
It explains the historical link between the two movements, citing early attempts by Patrick DuBois and Andrew Clay Schafer to connect Agile infrastructure concepts at Agile2008, and how the term “DevOps” later emerged while the connection remained.
The piece then compares Scrum with broader Agile practices, emphasizing that Scrum improves collaboration and focus but can become a rigid doctrine without technical practices such as code review, automated testing, and continuous integration.
Unplanned work—such as performance spikes, outages, and security incidents—is highlighted as a driver for adopting DevOps thinking alongside Scrum or Kanban, leading many teams to adopt hybrid approaches like Scrumban or Kanplan.
Atlassian’s experience is described, where product owners focus on functional features while service owners prioritize non‑functional aspects (performance, reliability, security), illustrating a “two‑owner” model that helps balance priorities without hindering DevOps adoption.
The article stresses that DevOps is more than continuous delivery; while CD automates pipelines and reduces work‑in‑progress, a mature DevOps culture also requires value‑focused maturity, avoiding endless technical improvement loops that do not benefit the business.
Three layers of DevOps are presented (as defined by Gene Kim): 1) Continuous Delivery – workflow automation from development to operations. 2) Practice – developers participate in operational issues, improving observability and response. 3) Systemic Experimentation – continuous improvement across the whole product delivery system, not just isolated changes.
Finally, the article concludes that Agile and DevOps are cultural movements that share a focus on embracing change, delivering value, and fostering collaboration; understanding their deeper principles helps avoid conflict and enables teams to combine their strengths effectively.
Signed-in readers can open the original source through BestHub's protected redirect.
This article has been distilled and summarized from source material, then republished for learning and reference. If you believe it infringes your rights, please contactand we will review it promptly.
DevOps
Share premium content and events on trends, applications, and practices in development efficiency, AI and related technologies. The IDCF International DevOps Coach Federation trains end‑to‑end development‑efficiency talent, linking high‑performance organizations and individuals to achieve excellence.
How this landed with the community
Was this worth your time?
0 Comments
Thoughtful readers leave field notes, pushback, and hard-won operational detail here.
