As organizations move towards a faster flow of automated software delivery, agile change management has become an imperative. So how do you achieve it?
Change management controls the gateway between development and deployment. It does not assess the technical worthiness of a change, nor does it build, test, and deploy a release. Its objective is to control, manage, and mitigate the risk of changes to the production environment.
One of the biggest challenges in software development is the nearly impossible task of gathering clear requirements and then getting those requirements to remain unchanged during code development. In the waterfall approach to software development—despite efforts to define, document, and approve every possible contingency before development begins—the delivered product is rarely what the customer wants.
Recently there’s been some new thinking around agile methodologies and processes to possibly bring those disillusioned with agile and scrum back into the fold. Two movements have emerged: Agile 2016 keynote speaker, Joshua Kerievsky’s “Modern Agile” and Agile Manifesto signatory Alistair Cockburn’s “Heart of Agile.”
Agile, DevOps, continuous delivery—and all of it at scale. How do these things come together? Businesses want to do more with the technical advances that DevOps and agile have conferred, but when it comes to next steps, those who advocate “scaled agility” seem to talk past those who discuss “the DevOps enterprise.”
