DevOps 3C's Process Explained
The above image explains what tool set is required to achieve the DevOps 3C's process. How 3C's help in making the process continuous of development, testing and promoting to various environment.
Saturday, January 24, 2015
Introduction
DevOps 3C's are pillars to achieve complete automation.
These days people wants fast output. No one like to wait for 1 or 2 days for a letter to arrive but instead would use mobile messaging or emails to get information in seconds. With that concept in mind DevOps 3C's plays a major role in getting fast outcome in day to day changing business needs.
Why 3C's belong to DevOps, as it integrates the cycle from
business needs > developer > ops > business outcomes
People lot of time confuse that all of the above 3C's we had it before then why it comes along as major part with DevOps. Yes lots of processes had already in place i.e as in developer life they use Jenkins/Bamboo to achieve Continuous Integration, Testers have their scripts which they run every release to measure the quality of the application for Continuous Testing and Ops folks have shell scripts/python/chef to automate their process of creating the application servers for Continuous Delivery, so then what DevOps 3C's will achieve if we already have automation in place?
So to clearly understand DevOps 3C's, its not a new tool, its about setting common processes, standards and agreed upon tools to achieve the DevOps 3C's. Its a cultural change which is required between teams, need to have a common goal of achieving business needs as fast as possible.
The main thing is to combine the process what developer / tester / ops use to do and making it more robust, repetitive and predictable. It has challenges around connecting these 3C's in any organizations but if done well the business would see a sure impact in achieving sales target for the companies.
Subscribe to:
Comments (Atom)