History of #DevOps

History of #DevOps

History of #DevOps

The Origin

The evolution of the Software Development Life Cycle (SDLC) rapidly changes the landscape on how the organization release/produce theirs to the Production environment. The traditional SDLC commonly tied to the Waterfall approach when coming to how the organization managed its product delivery. With this Waterfall, it not aligned with the organization business goals, which they want more speed and features/product to their customer. With this mindset, they need a new approach to speed up the product delivery but at the same time, improve the Developer and IT Operation team. Therefore, DevOps comes into the picture, the alphabet "DevOps" introduced by Petrick Debois at Agile Conference, Toronto in 2008.

The first conference named Devopsdays held in Ghent, Belgium, in 2009. Belgian consultant, project manager, and agile practitioner Patrick Debois founded the conference.  The conference has now spread to other countries. In 2012, the State of DevOps report was drawn up and launched by Alanna Brown at Puppet. As of 2014, the annual State of DevOps report was published by Nicole Forsgren, Gene Kim, Jez Humble and others. In 2014, they found that the adoption of DevOps was accelerating. Also in 2014, Lisa Crispin and Janet Gregory wrote More Agile Testing, which included a chapter on testing and DevOps.

If I put above chronology event into Timeline, it depictures below;

DevOps-timeline-1

What is DevOps?

DevOps is also a mix of emerging technology and rising business culture. The idea to move to DevOps culture is to create open communication, transparency and interdisciplinary teamwork. The concept behind DevOps breaks down silos and creates more spaces for discussion and collaboration between Developer (DEV) and IT Operation (OPS). The power of DevOps lies in the culture that supports it, shifting the mentality away from the silos. It often helps you understand where this came from and why it grew to popularity to understand what something is.

What it's the purpose?

DevOps can solve for your organization's challenges you are facing when you implement DevOps culture and approach, and the organization will get:

  • Faster delivery of services: Agile releases that keep up with rapid demand. Visibility across data: ensuring compliance and data accuracy.
  • Service efficiency: increased quality and performance.
  • Experienced professional DevOps: Teach you the tools that you need to succeed.
  • All adapted to your organization's specific needs.

DevOps IS

  • A concept
  • A mindset
  • A shared attitude understood and embraced by individuals
  • A culture that must be nurtured and iteratively improved
  • Visibility
  • Mentoring
  • Learning
  • Inclusive and open to all ideas
  • Iterative
  • Continuous
  • Collaborative
  • An excellent way to confidently develop and deliver software

DevOps is NOT

  • Easily achieved nor implemented
  • A product or toolchain
  • A job title or role
  • A cloud infrastructure solution
  • A technology
  • A programming language
  • A marketing campaign
  • CI/CD Pipeline
  • Kubernetes
  • Containers/Docker
  • Open-source software
  • Infrastructure as Code
  • Automation

In Nutshell

DevOps is that the IT industry desperately needed conceptual continuous learning and improvement. And the IT community can undoubtedly learn a lot from DevOps history. This DevOps revolution is not surprising that its importance will increase in the future with growing innovations. We have seen how security combined with DevOps could forever change the Infosec industry.

Conclusion

It is reasonable to describe DevOps as a journey, or perhaps an aspiration, rather than a defined destination or tools. DevOps seeks continuous improvement, seeking higher output, greater efficiency and even continuous deployment. Automated tools that support DevOps are continuing to evolve.


Share Tweet Send
0 Comments
Loading...