This article is based on reporting originally published by meritalk.com, drawing on discussions at the Federal Focus: The Cloud Generation event.
Federal IT Leadership Is Changing Its Language on Cloud
Something is shifting in how federal IT leaders talk about modernization. The cautious, hedge-everything language of the past is giving way to something more decisive. At a recent Federal Focus: The Cloud Generation event, agency leaders described not gradual migration strategies but full commitment — burning bridges back to legacy approaches and moving forward without a fallback plan.
That tone matters. Federal IT modernization has historically been slow, risk-averse, and plagued by incomplete projects. DevOps — and the cultural shift it demands — is being positioned as one of the primary levers to change that pattern.
SBA’s 57-Day Cloud Migration: What “Full Commitment” Looks Like
At the event, Small Business Administration (SBA) Deputy CIO Guy Cavallo and CTO Sanjay Gupta described their agency’s data center-to-cloud migration. Their advice was blunt: the key to success was to “burn the bridge back to the old way of doing things” and commit completely to the new model.
The SBA completed its migration in 57 business days without additional funding. That timeline is notable not because every agency should expect identical results, but because it demonstrates that speed is possible when leadership is aligned and the organizational will exists. The SBA’s migration happened against the backdrop of the Data Center Optimization Initiative (DCOI), a federal directive pushing agencies toward cloud-first infrastructure strategies.
DevOps Is More Than a Software Development Methodology
Jennifer Hoover, DevOps Program Manager at the Transportation Security Administration (TSA), offered an important clarification during the panel: DevOps is not just a set of software development practices. The true scope is significantly broader.
- Tools: The platforms and automation toolchains teams use to build, test, and deploy software.
- Technology: The underlying infrastructure, including cloud platforms and containerization.
- Processes: How services are acquired, how work is prioritized, and how releases are managed.
- People: The teams operating the systems and the organizational structures that govern how they interact.
“Inherently, DevOps is about the people. It’s about the culture. Somewhere in the middle of that is DevOps.”
— Jennifer Hoover, DevOps Program Manager, TSA
This framing is consistent with how DevOps practitioners across industries describe the discipline. Technology tooling is the visible surface; culture and process are the harder, more important work underneath.
Breaking Down Silos: DevOps as a Collaboration Framework
Sean Jennings, co-founder and Senior Vice President of Solutions Architecture at Virtustream, described a problem that will be familiar to anyone who has worked in traditional enterprise or government IT: tools built in isolation that don’t meet functional needs, and development projects executed in silos and abandoned before completion.
DevOps addresses this directly by connecting customers, engineers, operations teams, security teams, and service staff throughout the development lifecycle — not just at the beginning or end. This continuous involvement has several practical benefits:
- End products are more likely to meet actual mission needs, not just technical specifications.
- Flaws and requirement gaps surface earlier, when they are cheaper and less disruptive to fix.
- Security teams are embedded in the process rather than brought in at the end as a gate — a practice increasingly referred to as DevSecOps in federal contexts.
- The incremental delivery model replaces the all-or-nothing risk profile of traditional waterfall projects.
The contrast with waterfall development is significant. In a waterfall model, a project can run for years before stakeholders see a working product — by which time requirements have changed, budgets have shifted, and political priorities have moved on. DevOps shrinks the window between idea and delivery, which is particularly valuable in a government environment where mission priorities can change quickly.
The Hardest Part: Culture Change and Communication
Chad Sheridan, CIO of the USDA Risk Management Agency, was candid about the challenge: DevOps requires an enormous shift in mindset, and that shift doesn’t happen through policy memos. His primary job, as he described it, is to constantly communicate the “why” — helping different groups understand each other’s perspectives and build trust in the new approach.
Both Sheridan and Hoover emphasized practical communication strategies they’ve used to build that trust:
- All-hands meetings to share progress and address concerns openly.
- Lightning talks to spread knowledge quickly across teams.
- Guest speakers who can offer external perspective and credibility.
- Ongoing interaction between groups that previously worked in isolation.
This is not incidental to DevOps success — it is central to it. Teams that adopt DevOps tooling without addressing the underlying cultural and communication barriers typically see limited gains. The toolchain is only as effective as the collaboration it enables.
DevOps in a Multi-Cloud Federal Environment
Federal agencies are not moving toward a single cloud provider — they are navigating a multi-cloud reality, with different workloads distributed across commercial and government cloud platforms. This adds complexity to both development and operations.
DevOps practices — particularly continuous integration and continuous delivery (CI/CD) pipelines, infrastructure-as-code, and automated testing — are well suited to this environment. They make it possible to deploy and scale services rapidly across cloud environments without the manual, error-prone processes that characterized legacy federal IT.
The broader goal, as framed at the Federal Focus event, is digital transformation: agencies not just moving existing applications to the cloud, but fundamentally rethinking how they build and deliver services to citizens and internal users. DevOps provides the operational foundation for that transformation — but only if the cultural and leadership prerequisites are in place first.
Key Takeaways for Federal DevOps Practitioners
- Full commitment matters. Half-hearted migrations that preserve too many legacy dependencies tend to inherit legacy problems. The SBA’s approach — complete commitment, no fallback — produced measurable results.
- DevOps scope is broader than most teams initially expect. Tools are the easy part. Process, acquisition, and culture require sustained leadership attention.
- Continuous stakeholder involvement is non-negotiable. Building technically correct systems that miss mission needs is a predictable failure mode in siloed organizations. DevOps addresses this structurally.
- Communication is a core competency, not a soft skill. CIOs and program managers who can explain the “why” and facilitate cross-team understanding are essential to DevOps adoption.
- The DCOI and cloud-first mandates create urgency. DevOps is not just a best practice — in the federal context, it is increasingly the mechanism for meeting compliance and modernization deadlines.