My 50 cents on DevOps Transformation!
How long do you think it would take for your business to deploy a change in pre-production or production that involves one line of code?
The cycle time is the one that determines the time it takes from deciding that you need to modify something to having it in production. So it’s a vital parameter for any project.
Cycle times are measured in weeks or months in many companies, and there is definitely no regular or dependable release process. It is manual, aka old fashioned, & often requires quite a big squad to deploy the application even in a testing or staging environment, let alone into production.
In my experience, we have come across equally complex projects that started like this. After a comprehensive reengineering exercise, aka DevOps Transformation journey, teams could achieve a cycle time of hours or even minutes for a critical fix. This became possible because a fully automated, repeatable, reliable process was created to make changes through the multiple stages of the build, deploy, test, and release process.
In this entire process, Automation is the key. It empowered the developers, testers & operations team to deploy the application at a click of a button.
By implementing DevOps Transformation, any company can revolutionize its software delivery by shortening and securing the path from idea to realized business value, aka the cycle time.
Reference — Continuous Delivery by Martin Fowler
