This article is based on reporting originally published by JAXenter and draws on statements made at the DevOps Enterprise Summit.
The Innovation Problem in Financial Services
Finance is an industry that underpins everyday life — for individuals, businesses, and governments alike. Yet despite its scale and economic importance, it has been remarkably slow to modernise its software delivery practices. The reasons are structural, cultural, and, in many ways, entirely logical.
Banking is dominated by large, deeply entrenched institutions with vast regulatory obligations and zero appetite for service disruption. When your systems move billions of pounds or dollars every day, stability is not a nice-to-have — it is the entire product. This creates a natural conservatism: if a system has worked reliably for decades, the incentive to change it is low, and the perceived risk of change is high.
Security threats compound this. Financial organisations are among the most targeted by cybercriminals, which means any new system or software release is scrutinised intensely for vulnerabilities. The result is long release cycles, extensive manual testing gates, and organisational cultures where caution is rewarded and speed is viewed with suspicion.
Why Innovation Stalls: Legacy Systems and Silo Culture
Legacy technology is perhaps the single biggest barrier to DevOps adoption in finance. Core banking platforms, some dating back decades, were not designed for continuous delivery, containerisation, or cloud-native deployment. Wrapping modern DevOps toolchains around these systems is technically complex and expensive.
Equally damaging are organisational silos. In traditional financial institutions, development, operations, compliance, security, and audit teams frequently work in isolation, each optimising for their own objectives. This fragmentation makes the cross-functional collaboration that DevOps requires genuinely difficult to implement — it is not just a tooling problem, it is a governance and culture problem.
Unlike consumer industries such as retail or entertainment — where digital disruption created obvious new revenue streams — established banks historically saw little commercial pressure to change delivery practices. That calculus is shifting rapidly as fintech challengers erode customer loyalty and regulators push for faster, more transparent systems.
Building the Case for DevOps in Finance
Some of the world’s largest financial institutions have now moved beyond pilot programmes and made DevOps a company-wide commitment. Their experiences offer a useful blueprint.
Capital One: From Agile Pocket to Enterprise Transformation
Capital One’s DevOps journey began with a small team of developers experimenting with agile practices. Over roughly three years, those practices scaled across the entire enterprise. The organisation moved deliberately toward open-source tooling and automation, with the explicit goal of responding faster to bugs, increasing release repeatability, and improving overall software quality.
Tapabrata Pal, Senior Director of Agile at Capital One, described the cultural challenge at the DevOps Enterprise Summit: “There were pockets of resistance but since we got leadership buy-in those resistances didn’t last long.” This point is critical. In large organisations, DevOps transformation stalls without visible, sustained executive sponsorship. Technical tooling alone cannot dissolve silos that have been reinforced by years of incentive structures and reporting hierarchies.
Barclays: DevOps Across the Entire Business
At the same DevOps Enterprise Summit, Jonathan Smart, then Head of Development at Barclays, described the bank’s ambition in unusually broad terms. The initiative was not confined to engineering teams: “We’re not doing agile for agile’s sake. We’re pursuing a strategy for the whole business to exhibit agility. When I say the whole business, I mean HR, auditing, security, compliance, the investment bank, the retail bank — everything.”
With more than 800 teams involved in some form of DevOps practice, Smart reported that the shift had produced a measurably better way of working, reducing risk and increasing quality. For a bank whose services must be available 24 hours a day, seven days a week, even a brief, unplanned outage carries significant financial and reputational cost. DevOps practices — particularly continuous integration, automated testing, and progressive delivery — directly address this risk by catching defects earlier and making deployments smaller and more controllable.
What DevOps Actually Delivers for Financial Services
The value proposition of DevOps for finance is not primarily about shipping features faster, though that matters. It is about gaining end-to-end visibility and control over complex, high-stakes software systems. Specific benefits include:
- Silo removal: Breaking down walls between development, operations, security, and compliance teams enables faster feedback loops and shared accountability for production reliability.
- Automation: Automated testing, deployment pipelines, and infrastructure-as-code reduce manual error and make releases repeatable and auditable — both important for regulated industries.
- Scalability: Cloud-native DevOps practices allow financial organisations to scale capacity in response to demand peaks (e.g., end-of-month processing, market volatility events) without over-provisioning permanently.
- Risk reduction: Smaller, more frequent releases with automated rollback capabilities reduce the blast radius of any single deployment, making change safer rather than riskier.
- Regulatory alignment: Automated audit trails, change management logs, and reproducible build pipelines can simplify compliance with frameworks such as PCI-DSS, SOX, and DORA (the EU Digital Operational Resilience Act).
How Finance Professionals Can Drive DevOps Adoption
The fintech landscape is accelerating competitive pressure. Mobile-first banks, digital payment platforms, and API-driven financial products have raised customer expectations for seamless, always-available services. Traditional institutions must respond. Here is how to approach the transition deliberately.
1. Secure Leadership Buy-In Before Scaling
Both Capital One and Barclays found that resistance faded when executive leadership made a visible, sustained commitment to DevOps principles. Without this, transformation efforts tend to stall at the team level — producing isolated pockets of good practice that never achieve the cross-functional benefits DevOps promises. Build the business case in terms leadership understands: reduced outage risk, faster time to compliance, and competitive positioning against fintech challengers.
2. Choose Tools That Fit Your Context
There is no universal DevOps toolchain. A large retail bank with decades of mainframe legacy has different constraints from a digital-native challenger bank. Invest time in assessing which tools genuinely address your bottlenecks before committing to an enterprise-wide rollout. Rushing aggressive tool adoption can actually slow cultural change by generating frustration and cynicism among the teams you need to bring along.
3. Treat Culture Change as the Primary Workstream
DevOps tools are relatively easy to procure. Changing how hundreds or thousands of people collaborate, prioritise, and share information is the hard part. Invest in training, communities of practice, and clear communication about why the organisation is changing. Make it safe to experiment and safe to fail in low-risk contexts. Cultural transformation cannot be mandated; it must be modelled and reinforced consistently over time.
4. Start with Measurable Outcomes
Define what success looks like before you start. Deployment frequency, change failure rate, mean time to recovery (MTTR), and lead time for changes (the DORA metrics) provide an objective baseline against which to measure progress. In a sector where every claim must be evidenced, having quantifiable outcomes makes it easier to sustain investment and demonstrate return.
5. Embed Security and Compliance from the Start
In financial services, security and compliance cannot be retrofitted into a DevOps pipeline as an afterthought. Adopt a DevSecOps approach from day one: integrate static analysis, dependency scanning, secrets management, and automated compliance checks into the CI/CD pipeline. This makes security a shared engineering responsibility rather than a gate applied by a separate team at the end of a release cycle.
Conclusion
The financial services sector’s reluctance to embrace DevOps has always been rooted in understandable caution. But the evidence from organisations like Capital One and Barclays demonstrates that DevOps, implemented thoughtfully and with genuine leadership commitment, makes financial systems more secure, more resilient, and more responsive — not less. With competitive pressure from fintech challengers and rising customer expectations, the cost of standing still now outweighs the cost of change. The question is no longer whether finance should adopt a DevOps culture, but how quickly it can do so without sacrificing the stability its customers depend on.