Big Bang or DevOps
Many blogs and websites talk about DevOps, often focussing on automation, PaaS and the process efficiencies of working in new ways. When we set up our DevOps Practice (to establish good practices and so drive continuous innovation for our customer projects), we noticed an emerging pattern. Traditional Ops functions (across disciplines including Networking; Security; Storage; Virtualization and Operating Systems) were shifted left into the build pipeline, freeing staff (who had the skills) to shift right into higher-value functions such as Policy-driven Architecture and Automation Engineering. To be successful, this transformation requires teams to adapt their development process (perhaps now delivering containers into a PaaS) and to work out which roles are needed to make this work. Our experience of Agile team dynamics as well as the tools and processes has enabled us to accelerate this transformation process.
We’ve also found that a “big bang” approach doesn’t work well. Instead, it’s better to establish a DevOps strategy on a single system and then adapt, develop and understand it before migrating other systems to it. The following (4 ½ min) video describes this; let us know what you think.