Authenticating Agile Principles for Government Transformation
Co-authored with Lindy Quick. Originally presented at the 2025 IEEE Conference.
In 2023, we introduced the Government Operations and Vision (GovOps) Framework. The argument was straightforward: the limitations to government agility are self-imposed, and a systematic approach built for the unique context of government, not borrowed from private industry, could overcome them.
This paper is the follow-up. What we’ve done since is go back into the field across multiple government and near-government organizations to validate and deepen the framework. The result is eight core principles that extend the original five pillars into a more actionable operating model, and five case studies that show what those principles produce in practice.
The short version: one agency delivered more in 18 months than in the prior seven years. Another completed in six months what had taken three years. A third recovered six weeks of schedule and $500,000 within three months of adopting GovOps. A fourth reduced its technology application count from over 2,000 to just over 1,300 and achieved a 30% reduction in operating expenses.
These are not exceptional organizations. They are representative of what becomes possible when agile is designed for government, not imposed on it.
Why Agile Needs to Look Different in Government
Agile methodologies and scaled agile frameworks were designed for the private sector. Their assumptions include profit as a primary motivator, relative organizational stability, and the ability to rapidly change structures and contracts. In government, none of those assumptions hold uniformly.
Value in government is not profit. It is mission fulfillment. Leadership changes with election cycles. Contracts are bound by procurement law. Vendors cannot be swapped as easily as in a commercial context. And the hierarchy of command, especially in defense and federal agencies, is not an obstacle to remove but a structural reality to design around.
Principles designed for private industry can only bend so far before they break. That’s why we developed eight principles built specifically for the government context.
The Updated GovOps Framework
Before the eight principles, the five pillars of GovOps received updated sub-dimensions based on what we learned from implementation. Each pillar now carries three sub-dimensions that create the operational understanding necessary to be agile within that space.
The Contracts pillar, for example, now explicitly addresses flipping the “Iron Triangle” of project management: in private sector Agile, scope is fixed and time and cost are flexible. In government, this gets inverted. By funding people, not projects, and embracing incrementally adjusting contracts rather than rigid multi-year commitments, agencies create room for the kind of flexibility that agile actually requires.
The Vendor Management pillar now elevates “Vendor Alignment Over Vendor Agreement.” Most organizations spend their energy on SLAs and deliverables. The sub-dimension of alignment requires something harder: connecting vendors directly to the mission outcomes they are helping achieve and measuring them against that.
The 8 Principles of GovOps
Principle 1: Drive Mission Centricity
Every process, experience, and outcome should be aligned with the overarching mission. When all efforts are mission-driven, the organization reduces waste by eliminating activities that don’t directly support the mission. Mission Centricity also provides a clear baseline against which to measure iterative progress and drives meaningful collaboration both within and between organizations.
This is the most foundational principle. In practice, it means regularly assessing whether ongoing initiatives are actually advancing the mission, and being willing to stop work that isn’t.
Principle 2: Champion Adaptive Leadership
Leadership in government must be adaptive, not just administrative. Adaptive leaders navigate dynamic and changing environments, foster cultures that embrace change, and drive innovation. They prioritize proactive, data-driven decision-making while empowering teams to make the right decisions with guidance rather than directives.
This principle directly addresses one of the core structural barriers to government agility: the chain of command culture. Adaptive leadership doesn’t eliminate hierarchy. It changes what leaders do within it.
Principle 3: Optimize the Whole
Government organizations must move beyond siloed thinking. Rather than focusing on individual tasks or departments, this principle encourages viewing the organization as a unified system where every component and function is interconnected. By applying systems thinking across the whole, it becomes easier to visualize inefficiencies, redundancies, and areas of opportunity that siloed analysis would miss entirely.
There are significant barriers to communication between different parts of the same government organization. This principle encourages removing those barriers wherever possible and creating a common view of value across departments.
Principle 4: Prioritize Transparency and Resiliency
In government, transparency and resiliency are not just ideals. They are essential to building trust and ensuring continuity of operations. This principle creates a culture of openness and accountability while building systems robust enough to respond to disruption without sacrificing operational readiness.
Importantly, this principle is articulated as prioritizing transparency, not requiring it. Certain missions and contexts require confidentiality. The goal is maximum transparency within those constraints, not transparency as an absolute.
Principle 5: Create a Continuous Improvement Culture
Agility is inherently tied to continuous improvement. This means that excellence is not a one-time achievement. It requires encouraging every member of the organization to identify inefficiencies, suggest improvements, and actively participate in evolving operational processes.
The fear of massive change frequently prevents organizations from getting started. A culture that values small, incremental changes that accumulate into large ones is powerful precisely because it removes that barrier to entry. This principle applies iterative thinking not just to delivery but to process improvement and culture transformation.
Principle 6: Practice Agile Procurement
Traditional procurement is one of the biggest barriers to government agility. Given that much of the government workforce consists of third-party vendors, suppliers, and contractors, pre-determined and locked-in contracts create inflexible systems of delivery that cannot respond to changing circumstances.
Agile procurement gives government organizations the ability to modify contracts and procurement strategies as priorities, technologies, and opportunities evolve. It also drives more agile behaviors within vendors, forcing them to be more flexible in delivery and partnership. The best path forward becomes deliberate collaboration between all the parties necessary to support the mission, rather than each party optimizing for its own contract deliverables.
Principle 7: Leverage Data and AI for Better Decisions
For a government organization to be agile, it needs the ability to make quick, informed decisions. Data and AI create opportunities for identifying future trends, risks, and opportunities. They also allow organizations to start change processes at the moment they would have the most impact, rather than reacting after the fact.
This principle also enables a more personal, responsive, and timely approach to serving constituents. When data is available and synthesized, leaders don’t have to wait for quarterly reports to understand what is working and what isn’t.
Principle 8: Support Cross-Agency Collaboration
Without it, agencies solve the same problems independently, starting from scratch because there are no mechanisms for knowledge retention and sharing. Cross-agency collaboration breaks down silos, accelerates decision-making, and reduces duplication of effort. When agencies share best practices, success patterns, lessons learned, and pitfalls of delivery, they enable innovation through alignment. Each agency can identify the best path forward for its unique context by drawing on knowledge gained across the system.
Five Case Studies
Program A: Accelerating Hardware Deployment
A large government agency faced significant delays in hardware deployment due to complex dependencies across multiple departments. Project managers struggled to identify bottlenecks early, and issues typically surfaced only after deadlines were missed.
After adopting GovOps, the agency introduced a collaborative planning event where all teams involved in deployment came together to map dependencies and plan integrated sprints. What had taken months to coordinate and deliver was now being completed in days.
As one project manager put it: “Until this planning event with all of our people, we had no idea we would have missed our dates due to these dependencies.”
Program B: Reversing Seven Years of Stagnation
A large government agency had been working on a critical modernization project to replace a decades-old legacy system for seven years. Multiple teams were working in silos, following different processes, with unclear dependencies and no consistent delivery.
The agency adopted GovOps and, critically, took on the role of primary integrator rather than relying on a single contractor. By incorporating multiple contractors into a unified team of agile teams, the agency created a structure where every contractor was required to collaborate, sync regularly, and integrate deliverables in support of shared mission goals.
The result: “By aligning and delivering using Agile, we released more in 18 months than in the past seven years.”
Program C: Recovering a Government Contract
A government contractor was six months behind schedule on a critical federal project with a $2 million cost overrun. Multiple teams and subcontractors were involved but barely coordinating. Dependencies were hidden. There was no shared language for discussing the work.
The contractor organized a workshop that brought all teams and subcontractors together to collaboratively map the entire process from start to finish. As one project manager reflected: “We have been working on this for six months, and until we mapped out the entire process, we didn’t know how to talk about the work.”
With daily stand-ups, sprint reviews, retrospectives, and regular subcontractor integration into the agile workflow, the contractor recovered six weeks of lost time and saved $500,000 within three months.
Program D: Six Months Instead of Three Years
A large government agency had been using waterfall project management with multiple teams working in isolation. The result: long lead times, duplicated effort, and misaligned priorities. Team members were split across multiple projects simultaneously, which fragmented attention and slowed delivery.
By adopting GovOps, the agency realigned all work to its mission, restructured teams so each member was dedicated to one project, and implemented continuous feedback loops to surface issues quickly rather than waiting until after significant work was complete.
As one agency leader said: “That’s incredible. We were able to deliver in six months what took three years previously.”
Program E: 30% Cost Reduction Through Mission Alignment
A large government contractor had grown through mergers and acquisitions into an organization with over 2,000 technology applications distributed across the business, with significant redundancies and few economies of scale.
By applying GovOps Principles 1, 3, 4, and 7 — Mission Centricity, Optimize the Whole, Prioritize Transparency and Resiliency, and Leverage Data and AI for Better Decisions — the technology group mapped all applications into engineering capabilities aligned to the strategic mission, then streamlined each capability for consistent application and reuse.
The outcomes: the application count dropped from over 2,000 to just over 1,300, a 35% reduction. Operating expenses decreased by 30%. Time to value delivery improved by nearly 50%.
What These Cases Demonstrate
Each of these programs was struggling with a version of the same fundamental problem: work was being done in isolation from the mission it was supposed to serve. Teams were optimizing locally without visibility into the system as a whole. Vendors were meeting contract deliverables without understanding how those deliverables fit together for a common outcome. Leaders were managing work rather than understanding and responding to changing circumstances.
GovOps does not resolve these problems with a process checklist. It resolves them by creating the conditions under which people can see the whole system, align to a shared mission, and build enough trust and transparency to course-correct continuously.
The framework equips government organizations with the tools and methodologies necessary to deliver value more efficiently and effectively. By embracing agile principles tailored specifically for government, agencies can better meet constituent needs, respond to unforeseen challenges, and achieve mission success in ways that would have been previously unimaginable.
The demand for Government Agility has never been greater. What these case studies demonstrate is that the demand can be met, and the path to meeting it exists. The evidence is there. The question now is whether enough organizations are willing to stop treating bureaucracy as an immovable constraint and start treating it as the self-imposed limitation it actually is.