The idea of DevOps culture is not a brainchild of a single person and the concept has not arrived overnight. The initial contribution to DevOps culture has started in the year 2007 as an initiative towards improving the workflow in the IT processes. DevOps culture has not yet reached the final stage but it is still evolving that focuses on solving the problems that every professional in the IT industry faces every day. It encourages collaboration and the use of automation tools to build a pipeline of workflows and chains. In other words, DevOps can be understood as an extension of the Agile methodology. There is still a lot to add to the DevOps maturity model and make it more robust and useful to all organizations over time. Let’s discuss the history and future of DevOps year over year in this article.
- The Year 2007: Patrick Debois who is a software development consultant focused on learning all IT aspects. He had taken many different IT roles over fifteen years where he gained a holistic understanding of IT. His various roles include developer role, network specialist role, system administrator role, tester role, and project manager role. He has also worked as a consultant for a large datacenter migration. He took charge of the testing where he had spent his lot of time with Development and Operation. He had performed a deep analysis of the differences between the working of the Development and Operation teams, where he noticed a lot of frustration with the challenges of managing work across these two groups on this datacenter migration as they were working in silos. Continuous integration has gained popularity in the agile community and the Development team has moved closer to the deployment, but still, the divide between the operations and development was in place. Such a situation has provided Patrick an idea to formulate a better way for these two teams to work together in collaboration.
- The Year 2008: In the Agile 2008 Conference, Andrew Shafer shared an idea about an agile infrastructure “birds of a feather” session. Patrick Debois noticed this post and went to the session. The idea of “birds of a feather” was received poorly and Andrew didn’t even show up to his discussion. But, Patrick found this as a common topic of interest and he was so excited to see that he is not alone who is looking for the solution to resolve the challenges of Development and Operation working together. Patrick tracked down Andrew and they started a Google group named Agile System Administration.
- The Year 2009: In the O’Reilly Velocity Conference in San Jose, John Allspaw (senior vice president of technical operations) at Flickr, and Paul Hammond (director of engineering) at Flickr, gave a presentation about “10+ Deploys per Day: Dev and Ops Cooperation at Flickr.” The presentation focus was on how Development and Operation can collaborate to improve the software deployment. In Belgium, Patrick Debois followed the presentation via a live stream and he was very inspired to start his conference, #DevOpsDays. The conference acted as a mechanism to bring together an energetic group of forward-thinking minds who are trying to improve software deployment. This group of people kept their conversation going over Twitter with the hashtag #DevOpsDays. Later, ‘Days’ was dropped from the hashtag as an effort to save Twitter character space, and the hashtag became #DevOps.
- The year 2010: In the following year, DevOpsDays sessions were held in Australia and the U.S. Over the period, the DevOpsDays brigade kept on growing in many different countries and cities around the world. More and more people get united to find a solution and energized about DevOps until it had become a full-on popular movement.
- The year 2011: The DevOps movement kept on growing and it has been fueled by individuals and open source tools with very little or no attention from analysts or vendors. Further in the year 2011, the movement began to go mainstream that came to the attention of analysts Cameron Haight from Gartner and Jay Lyman of 451 Research. By this time, Big vendors had already started to market DevOps.
- The year 2012: By 2012 DevOps Days was still a very hot topic continued to grow across the globe.
- The year 2013: In the year 2013, the public curiosity for DevOps information had inspired many authors to write books on the DevOps topic. DevOps books such as The Phoenix Project by Gene Kim, Kevin Behr, and George Spafford and Implementing Lean Software Development by Mary and Tom Poppendiek are the popular example of DevOps book in the year 2013.
- The year 2014: By the year 2012, many big organizations such as Target, Nordstrom, and LEGO became some of the first organizations to bring the DevOps into the enterprise.
- The Year 2015 and onward: The journey of future of DevOps has continued further that is still evolving to cater to every day growing and changing needs of many organizations. Still, they are many challenges which are faced by the organization in implementing the DevOps, but those challenges result in an opportunity to add something new to this DevOps topic. It is still evolving, and in the future, it will further deliver many fruitful results to the organizations.
Conclusion
In this article, we discussed the history and future of the DevOps culture across the globe.
⇓ Subscribe Us ⇓
If you are not regular reader of this website then highly recommends you to Sign up for our free email newsletter!! Sign up just providing your email address below:
Happy Testing!!!
