We are summarizing few of the case studies from DEVOPS CASE STUDIES: The Journey to Positive Business Outcomes by IT Revolution. What case studies you have? Post in the comments below.Technology Practice Journey:APIs>Full Agile Practice Stack>Automation>CI/TDD>Lean, ConceptsChallenges:Culture of stopping changes whenever something broke. IT organization was too complex, with silos inside of silos Server provisions took many teams, and there was no end-to-end accountability Large amount of technology debt Journey: 4 Stages.Enabling and unleashing change agents, cultivating and growing a grassroots movement, getting top-down alignment, figuring out how to scale across the enterprise. What IT Leadership did?Started internal DevOps ProgramEngineers started to talk about infrastructure as a codeDid branding around technologyBottom-up matched with top down.DevOps and Agile started to become core talking points in townhallsaligned with Thoughtworks’ CI/CD Maturity Model to baseline measure products moved from a COBIT-based, highly-segmented model, to a product and service model Shifted their delivery model from waterfall and project-based to product-based using Scrum and Kanban models. Modern tech architecture: API based, loosely coupled, lightweight tooling, self-service, and optimized for cloud based and CI/CD practices. converging the Agile and DevOps movements Traditional training combined with hands-on immersive experiences.They also created an internal incubator environment, like a transformation emergence center, called the Dojo, which became the place they went to practice their craft Hashtags: #DevOps #CaseStudyRef: DEVOPS CASE STUDIES: The Journey to Positive Business Outcomes by IT Revolution. https://itrevolution.comDisclaimer: Neither Agileance Org nor the contributors to this post claim the ownership or validity of the content. All rights reserved by the content owner.