A Historical Overview of DevOps and Its Related Practices
This article traces the evolution of DevOps from its roots in Toyota’s Production System and early manufacturing practices through the emergence of Kanban, Waterfall, Scrum, Agile, Lean, and modern extensions like ChatOps, GitOps, FinOps and AiOps, highlighting key milestones and concepts.
When searching for "DevOps" on search engines, many related terms such as Agile, Scrum, Lean, and Kanban appear, which can increase the learning difficulty.
The article examines the historical development of DevOps by reviewing its evolution over time.
1948 – Toyota Production System (TPS) : An integrated socio‑technical system that introduced lean manufacturing concepts, focusing on eliminating waste and optimizing cost.
1960 – Kanban (Industrial Manufacturing) : Originated from Toyota’s production model and later adopted by software teams as a visual workflow tool.
1970 – Waterfall (Software) : A linear development model that is now generally discouraged for team projects, suitable only for single‑developer or one‑off static sites.
1986 – Scrum (Industrial Manufacturing) : A framework for managing complex product development, later adapted to software as part of Agile.
1991 – Lean Manufacturing : A systematic approach to reduce waste, derived from TPS, emphasizing value creation with minimal effort.
1995 – Scrum (Software) & Agile : Scrum became a popular Agile methodology, while Agile itself was formalized in the 2001 Agile Manifesto emphasizing individuals, working software, customer collaboration, and responsiveness to change.
2003 – Lean (Software) : Lean principles were incorporated into Agile practices, focusing on waste elimination, learning, delayed decisions, rapid releases, empowerment, embedded quality, and global optimization.
2006 – Kanban (Software) : Large‑scale adoption of Kanban in software, often used for weekly meetings but requiring proper implementation to be effective.
2009 – DevOps : Introduced as a cultural and organizational extension to Agile, emphasizing collaboration between development and operations.
Definitions from major vendors (Amazon, Google, Microsoft, Atlassian) are listed, and the article notes that DevOps differs from Agile.
2014 – ChatOps : A collaboration model that integrates people, tools, processes, and automation through chat platforms and bots.
2017 – GitOps : A cloud‑native continuous deployment approach that uses Git and deployment tools to provide a developer‑centric experience.
FinOps : Financial operations for cloud cost management, balancing speed, cost, and quality.
AiOps : An emerging practice that aims to apply AI techniques to operations, still in an incubation phase.
The conclusion reiterates that the article only provides a brief historical recap of DevOps without covering its concepts or core principles, and promises future articles on DevOps benefits, measurement, and personal impact.
At the end, the article includes promotional material inviting readers to join a technical community and provides a disclaimer about the source of shared materials.
IT Architects Alliance
Discussion and exchange on system, internet, large‑scale distributed, high‑availability, and high‑performance architectures, as well as big data, machine learning, AI, and architecture adjustments with internet technologies. Includes real‑world large‑scale architecture case studies. Open to architects who have ideas and enjoy sharing.
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.