Agile DevOps dovetails with Service Design via a common objective of prioritizing users needs, and translates those needs into working software that delivers new digital services.
The UK Government mandates the use of Agile for developing new digital services, and via their service manual provide this detailed guide.
It sets out to break down the artificial boundaries that develop profusely in large, hierarchical organizations, and instead self-organise around a ‘delivery pipeline’ of the work required to deploy code faster and with fewer errors.
In their blog the Home Office describes how they are implementing Agile and DevOps practices.
They’re defining how overall this evolution can be seen as a shift to ‘Continuous Delivery’ (CD). As the name suggests this means an approach where rather than a small number of infrequent, very large releases of new software, developers are pushing out new updates on an high frequency basis, sometimes many in one day, where a ‘microservices’ software architecture means they work with a small, modular code base rather than one large ‘monolith’ making this agility possible.
They are implementing Kubernetes, Docker, Terraform and AWS, working in agile, interdisciplinary teams to build and operate public facing services. Utilizing principles such as “infrastructure as code” they are able to provision resources consistently and efficiently and manage them through the full life-cycle, versioning and peer review, to create and maintain robust, auditable, scalable and cost-efficient, autoscaled and rightsized environments for both development and production.