Most organisations now recognise that responsiveness to user and customer needs makes the difference between success and failure.
In IT product and service delivery, it is the combination of Agile and DevOps approaches that offers this responsiveness. DevOps tooling and techniques have been used in the Agile software development industry for many years, but unless the wider organisation is aligned to the DevOps approach, its impact is greatly reduced.
That’s what I set out to explore and explain in our joint webinar with our colleagues at Mastek yesterday, Deliver more and fail less with DevOps. You can click through to watch a recording of the webinar below.
In the webinar, I expand on this key point that it’s vital for organisations to understand: DevOps is not just about tools and techniques, it’s about culture. The purpose of the DevOps team is to play a transformative role in establishing this culture through consultancy, governance and innovation – and often through helping to shape a new operating model. Once these have been established, DevOps as a distinct team is no longer required; it’s just how the organisation operates.
As I describe in the webinar, resistance to the establishment of a DevOps culture often derives from concerns that a move away from traditional change management and release processes (relying on manual testing, configuration and deployment) will compromise quality, security and data integrity.
In fact, the opposite is true. Automation of these activities actually enhances quality, security and data integrity. As Puppet and DORA’s State of DevOps Report 2017 states, organisations taking a DevOps approach spend 50% less time remediating security issues and 21% less time is spent in unplanned work and rework.
>> Watch the webinar recording here