Lots of unfamiliar nouns will appear while searching for keyword DevOps in google, such as Agile, Scrum, Lean, Kanban. Honestly, it will increase the difficulty of learning for starters. It will be a good idea to discover history of it while we cannot find an exact answer from internet.
Where does DevOps comes from?
DevOps is a systematic project and it is difficult to explain it in a single sentence. Let’s take a look at the history of DevOps in a glance.
1948 — TPS (Toyota Production System)
The Toyota Production System (TPS) is an integrated socio-technical system, developed by Toyota, that comprises its management philosophy and practices. The TPS is a management system that organizes manufacturing and logistics for the automobile manufacturer, including interaction with suppliers and customers.
From Wikipedia
In my opinion, manufacturing industry is ahead of software industry in automation. In the early 1948, Toyota adopted the TPS model and became the world’s three largest automakers together with Volkswagen in Germany and General Motors in the United States.
The core concept of TPS is to eliminate waste. In fact, in the procedure of software development, what we are seeking for is to eliminate waste. However, we gradually forgot about it.
1960 — Kanban (Manufactoring)
Kanban is derived from TPS. In 2006, The concept of Kanban appeared in the software development area.
As figure shows, the Kanban applications such as Jira and Trello used in software industry are derived from TPS.
1970 — Waterfall (Software Development)
In the early 1970, waterfall model was used in software development area. This model is quite easy to understand. Lots of projects in school is still using it.
When to use waterfall?
If project developed by one person or a project without maintenance could use waterfall model.
1986 — Scrum (Manufacturing)
In manufacturing, Scrum is an agile framework for developing, delivering and maintaining product quality.
In software development, daily standup is a part of Scrum.
1991 — Lean manufacturing
Lean production is a systematic production method whose goal is to reduce waste in the production process. This concept also comes from TPS.
The core of lean production is to create value with the least amount of work.
1995 — Scrum (Software Development)
Scrum is a part of agile methodologies. The Milestone, Epic, Spring, Task, and stand-ups we encountered in our daily life are from Scrum methodology.
1995 — Agile (Software Development)
In 2001, seventeen software developers met at Snowbird Resort in Utah to discuss topic of lightweight development methods. It was initiated by Jeff Sutherland, Ken Schwaber and Alistair Cockburn.
Based on their experience of developing software and helping others do that, the seventeen signatories to the manifesto proclaimed that they value:
- Individuals and interactions over processes and tools
- Working software over comprehensive documentation
- Customer collaboration over contract negotiation
- Responding to change over following a plan
Simply saying, Agile concentrate on collaboration in teams.
2003-Lean (Software Development)
In 2003, Lean became part of methodologies in Agile.
2006 — Kanban (Software Development)
2009 — DevOps（Software Development）
DevOps can be seen as an extension of Agile. Lots of IT industries defines DevOps from their experience.
DevOps vs Agile
2014 — ChatOps (Software Development)
ChatOps is a collaboration model that connects people, tools, process, and automation into a transparent workflow. This flow connects the work needed, the work happening, and the work done in a persistent location staffed by the people, bots, and related tools. The transparency tightens the feedback loop, improves information sharing, and enhances team collaboration. Not to mention team culture and cross-training.
From: Atlassian
2017 — GitOps (Software Development)
GitOps is a way of implementing Continuous Deployment for cloud native applications. It focuses on a developer-centric experience when operating infrastructure, by using tools developers are already familiar with, including Git and Continuous Deployment tools.
The core idea of GitOps is having a Git repository that always contains declarative descriptions of the infrastructure currently desired in the production environment and an automated process to make the production environment match the described state in the repository.
From: gitops.tech
FinOps
FinOps is the operating model for the cloud — a combination of systems, best practices, and culture to increase an organization’s ability to understand cloud costs and make tradeoffs.
From: apptio.com
AiOps
AIOps uses artificial intelligence to simplify IT operations management and accelerate and automate problem resolution in complex modern IT environments.
From: IBM
