This article is based on reporting originally published by Computer Weekly and draws on commentary from senior public sector technology leaders in the UK.
DevOps Moves from Niche to Mainstream
DevOps—the discipline that unifies software development and IT operations to shorten delivery cycles and improve reliability—has steadily moved from an experimental practice into a mainstream strategy for organisations of all sizes. Gartner predicted as early as 2015 that the methodology would follow this trajectory, and the data appears to support that view.
Research from hosting provider Claranet suggested that around 18% of public sector organisations had developed a DevOps approach at the time of their survey, compared with roughly a third of private sector organisations. Separately, research conducted by Splunk and the Ponemon Institute among UK IT decision-makers across local and national government departments found that 74% of respondents had either adopted DevOps or were planning to, with 54% indicating that DevOps spending would increase in the coming year.
The picture that emerges is one of a public sector that lags slightly behind private industry in adoption rates, but that is notably enthusiastic about making DevOps work—more so than it appears to be about many other IT initiatives.
What Is Driving Public Sector DevOps Adoption?
Aaron Powell, Chief Digital Officer at NHS Blood and Transplant (NHSBT), describes DevOps not as a prescribed methodology but as a culture and a “state” of operating. In his view, adoption is an evolution rather than a single transformation event.
“That evolution involves, progressively, adopting more agile development, increasing automation and continuous integration, simplifying structures and systems, and focusing on the flow of change over the stages it goes through.”
Aaron Powell, Chief Digital Officer, NHS Blood and Transplant
This incremental approach is particularly well suited to public sector organisations, where change carries significant risk and stakeholder scrutiny. As more citizen-facing services move online, the ability to deliver digital services faster and more reliably becomes a core mandate rather than a competitive advantage.
The Financial and Talent Challenges
The cultural transformation that DevOps demands takes time—and time, in a budget-constrained environment, is a luxury. Many public sector bodies operate under significant financial pressure, which creates downstream problems in attracting and retaining the specialist engineers that DevOps requires.
Graeme Park, a senior consultant at Mason Advisory, points out that civil service pay grades typically cannot match what experienced DevOps engineers can command in the private sector. This forces departments into a choice between costly outsourcing arrangements or investing in internal training programmes.
Not everyone agrees that pay is the defining barrier. Mayank Prakash, Chief Digital and Information Officer at the Department for Work and Pensions (DWP), acknowledged to Computer Weekly that recruiting top talent remains a challenge, but argued that the civil service has worked to shake off outdated stereotypes and offers a compelling proposition for engineers who want their work to have a meaningful social impact.
Graham Lane, Development Manager at the Greater London Authority (GLA), offers a concrete example of how internal training can succeed in practice:
“We have mainly acquired DevOps skills through the training of our existing staff and this has worked well. The development of in-house DevOps skills has been part of a broader programme to do with digital transformation and the adoption of agile methods.”
Graham Lane, Development Manager, Greater London Authority
Legacy Systems: The Hidden Weight
Beyond pay, one of the most persistent structural obstacles facing public sector DevOps teams is the burden of legacy technology. Jason Rolles, CEO of software development monitoring firm BlueOptima, describes the challenge plainly:
“The public sector is often saddled with a significant burden of legacy systems which must be maintained and, where possible, modernised.”
Jason Rolles, CEO, BlueOptima
Modern DevOps toolchains—including open source tools such as Git for source control and Jenkins for continuous integration—require an IT environment capable of supporting rapid, automated delivery pipelines. Legacy infrastructure, often built over decades and deeply integrated into core service delivery, actively works against the speed and flexibility that DevOps promises.
This creates a compounding problem: without adequate budget to modernise infrastructure, it becomes harder to attract skilled DevOps engineers; without skilled engineers, modernisation stalls. Departments can find themselves locked in a cycle that makes meaningful change difficult to initiate.
Operating at Scale: The DWP Example
For some public sector organisations, the scale of operations is itself a defining challenge—and, paradoxically, part of the appeal for engineers who want to work on genuinely complex problems.
Prakash describes the DWP’s situation in terms that give a sense of the engineering complexity involved:
“For us, the scale of our organisation is the major issue – we transact more than £170bn every year and have one of Europe’s largest IT estates, operating across 850 buildings and 90,000 desktops. That requires a lot of orchestration, and DevOps is key to this.”
Mayank Prakash, Chief Digital and Information Officer, Department for Work and Pensions
Prakash also notes that the DWP’s user base presents a profiling challenge unlike most commercial environments. Citizens interact with DWP services repeatedly, across multiple programmes, often over years or decades. That complexity demands a test-and-learn engineering culture rather than assumptions borrowed from commercial software development.
The department’s engineers work with modern DevOps tooling, open-source technologies, and test-driven development practices in an agile environment—demonstrating that public sector DevOps, done well, can be technically sophisticated.
Mission-Critical Operations Limit Experimentation
A fundamental structural difference between the public and private sectors is that the vast majority of public sector digital services are mission-critical from day one. There is no equivalent of a fintech innovation lab where banks can prototype new methodologies at a safe distance from core operations.
As Rolles puts it, exploratory innovation departments in the private sector serve as testbeds for new methodologies without placing core business operations at risk. Public sector organisations—responsible for citizen services, patient records, benefit payments, and other essential functions—do not have that option. Any change to production systems carries immediate societal risk.
Regulatory constraints compound this caution. NHSBT’s Powell acknowledges that more radical interpretations of DevOps may not translate directly into heavily regulated environments:
“There are flavours of DevOps, and the more ‘radical’ flavours may not lend themselves to the pace of change or regulation of some public sector organisations, but the principles behind it are still relevant for most.”
Aaron Powell, Chief Digital Officer, NHS Blood and Transplant
The Role of the Government Digital Service
In the UK, the Government Digital Service (GDS) provides guidance and standards designed to help public sector organisations navigate digital transformation, including DevOps adoption. The GDS Service Standard sets out principles that are closely aligned with DevOps values: using agile methods, iterating and improving services frequently, adopting open standards and platforms, and testing end-to-end service delivery.
The GLA’s Lane notes that many of the standard’s principles map naturally onto a DevOps approach, giving public sector teams a recognised framework to reference when making the case for culture and process change internally.
Why DevOps Is Still Worth the Effort
Despite the constraints, the consensus among public sector technology leaders is clear: DevOps adoption is worth pursuing, regardless of how incrementally it is implemented.
Prakash summarises the case for DevOps in public sector terms:
“By adopting a DevOps approach, we’re able to bring services to life more quickly and more reliably, respond more reactively to user needs and benefit from cloud capabilities. In this environment, the old service models and over-the-wall handovers don’t work efficiently. DevOps provides us with an opportunity.”
Mayank Prakash, Chief Digital and Information Officer, Department for Work and Pensions
The social purpose dimension also plays a role that has no direct private sector equivalent. Engineers joining a government department are not building a commercial product—they are contributing to infrastructure that affects the daily lives of millions of people. That mission, communicated effectively, can itself be a recruiting tool.
Key Takeaways for Public Sector DevOps Teams
- Treat DevOps as a cultural evolution, not a one-time project. Incremental adoption—starting with agile practices, CI/CD, and automation—reduces risk and builds organisational confidence.
- Internal training is a viable path. Upskilling existing staff has worked for organisations like the GLA and reduces dependency on costly outsourcing.
- Legacy modernisation is a prerequisite, not an afterthought. Without addressing legacy infrastructure, the full benefits of modern DevOps tooling cannot be realised.
- Adapt DevOps to your regulatory context. There is no single correct flavour of DevOps. Regulated, mission-critical environments require a more measured approach to continuous delivery.
- Leverage GDS standards. The UK Government Digital Service framework provides a publicly available set of principles that align well with DevOps values.
- Social purpose is a differentiator. Engineers motivated by impact, not just technology, are a real and addressable audience for public sector recruitment.