Why Agile in Government Is Different from Agile Everywhere Else

Ask people why Agile teams struggle in government, and you’ll usually hear “red tape.” It’s a fair guess, but it misses where the real difference is. 

Scrum works the same way in a federal agency as it does at a software company. Sprints, backlogs, reviews, and retrospectives all stay the same. What changes is everything around the team. In government, four forces shape Agile delivery in ways most commercial teams never face: 

  • There’s no profit motive to settle what “value” means 
  • Contracts define the team’s scope, and sometimes its roles, before work begins 
  • Oversight asks questions a two-week sprint can’t answer. 
  • Support for Agile adoption can disappear when a leader changes 

Teams that understand these forces can work with them. Teams that don’t usually decide Agile “doesn’t work here”, to the detriment of themselves and taxpayers.  

1. There’s no obvious answer for what “value’ means 

In the corporate world nearly all work objectives roll up into the goals of earning more or spending less. When considering the relative priority of two feature ideas competing for the team’s energy in a sprint, we can use that clarity to ask which idea does more for the business’s bottom line, and the debate has somewhere to land. 

Government work value rarely means dollars and cents. Instead, value might mean processing benefits faster, meeting a statutory deadline, protecting a mission capability, or reducing audit findings. Each is legitimate, and they often compete.  

Without a shared definition, the vision gets fuzzy at every level from enterprise strategy down to a single team’s backlog. That may turn every Sprint planning meeting into a ‘Groundhog’s Day’ style renegotiation of priorities that leaves the team swinging wildly between objectives, with none of them seeming to get any real advancement. 

This is the biggest difference, so deal with it first. Visualize whatever definitions of value are at play, map out how the work of each team is supposed to support each, and forge a consensus about which outcome should win in a fight when conflict arises. 

2. The contract shapes the team 

Since federal workforce shifts in the 1980s and early ’90s, nearly all government IT work has been done by contractors. A government Agile team usually exists because of a contract, and that contract sets the limits on scope, funding, timelines, methods, tools, etc. 

The biggest limit is the contract type. For roughly twenty years, many agencies have preferred Firm Fixed Price (FFP) contracts over cost-reimbursement models like Time & Materials. Much of the reason is to keep vendor budgets from growing without guaranteed results. FFP promises the buyer a defined product at a defined price. 

That cuts against a core Agile idea. An agency might spend 1-3 years defining what it wants, then hire a team to build exactly that. If the mission changes and users now need something else, the team has two options: It can continue building what’s now obsolete, or it can attempt to renegotiate the work in a way that still fits within the original fixed-scope, fixed-cost, and fixed-schedule arrangement.   

One option for avoiding this trap is to guide agencies toward a cost-reimbursement model set up as a series of short-task orders (say, 6-month increments).  That way there is much more flexibility around scope definition, but the buying agency’s liability is limited within a small level of expenditure. 

If FFP methods are the only option available, another option would be to steer the contract to be based around a ‘’Statement of Objectives’ (SOO), rather than a ‘Statement of Work’ (SOW). A SOO is focused on desired outcomes without defining the configuration of the product that will deliver those outcomes, whereas a SOW typically pre-defines a product down to the feature level. 

3. Navigating oversight  

Agencies have review and approvals processes that commercial teams would find excessive. It’s tempting to treat them as obstacles, but that’s not the whole truth.  

Those rules come from years of people balancing the mission against citizen safety and responsible use of taxpayer money. Many exist because something went wrong before them.  

Oversight usually causes trouble because of when a review is required, not because the review exists. 

A common example is the Definition of Done, the checklist a team’s work has to pass before work is considered finished at the end of each sprint. Agencies often add items like legal compliance review, user acceptance testing, or customer sign-off to that checklist. Those reviews rarely finish within a two-week sprint, so work that should be done stays open, and teams keep going back to it while trying to start something new. 

The fix is to notice that these reviews ask a different question than the rest of the checklist: 

  • Quality checks ask, “Did we build it correctly?” Passing tests and security scans are examples. The team can complete them within the sprint, so they belong in the Definition of Done. 
  • Sufficiency checks ask, “Did we build the right thing?” Legal review and user acceptance are examples. They work better as part of planning a release, when reviewers can look at a larger batch of finished work on a timeline that fits how they actually operate. 

Nothing gets skipped. Each review still happens, just at a stage where it can realistically be finished. The same idea applies to oversight in general: learn what each rule protects, then show that the new way of working protects it just as well. 

4. Commitment depends on who’s in charge 

Many government Agile efforts start because one motivated leader champions them. Then that leader rotates out. The replacement may be uneasy with how visible uncertainty is in Agile frameworks, and then the requests for status-ing begin: Where’s the project schedule? The Gantt chart?  

Sprints turn into waterfall phases cut into two-week pieces, morale drops, and the organization decides that ‘Agile doesn’t work here’. 

Agile transitions need support from all levels of leadership to succeed. At one agency I coached, a contract change took the organization from zero Agile teams to 21 overnight. Senior leaders backed the move, but the direct managers our teams worked with every day had never bought in and resisted every adaptation we tried to put in place.  As a result, teams were flailing, and the organization was quickly reaching a consensus that all of this ‘Agile stuff’ was a huge waste of time and money.  Correcting that situation took more than a year of training and coaching those managers one at a time before the teams could really get to work. 

Compare that with an Intelligence Community program I coached early in my career. Leaders on both the government and contractor sides understood why short cycles mattered: teams could spot a risk, put a working prototype in front of users and adjust from what they learned. Because the people around the team understood the approach, the early contract friction faded within a few months and the teams delivered. 

A tool for change agents in these situations is to recruit heroes.  Find stakeholders at every level of leadership who will benefit directly from the success of Agile teams, and support them.  Connect the dots between the team-level wins to Agency wins, and show how the ability to incrementalize risk saves us from making huge mistakes. 

What needs to change about Agile in government  

When people say an Agile practice won’t work in government, they’re usually wrong. What stands in the way is a leader clutching onto familiarity that makes them feel in control. 

The work that needs to change is the work around the team: 

  • Define value explicitly, since profit motives can’t do it for you. 
  • Before the contract is signed, push for terms that let plans change with the mission. 
  • Learn the history behind why things are done before you propose changes.  
  • Allocate oversight actions to where they make the most sense. 
  • Build understanding among the mid-level decisionmakers who own day-to-day outcomes. Executive endorsement alone won’t survive a leadership change. 

Why it matters 

When an agency builds the wrong thing, or builds the right thing badly, the public pays for it. You see it in a benefits claim stuck for months or a portal that crashes on deadline day. Short, iterative delivery catches both problems early. Getting Agility right in government means people get the services they rely on, and taxpayers get a real return on what they’ve paid for. 

Sprightbulb’s coaches have supported Agile delivery across dozens of federal, state and public-sector organizations. If your agency is working through any of this, we’d be glad to talk through it.  

More Blogs