What do elite military units and high-performing Scrum teams have in common? Both thrive in uncertainty, rely on trust and adaptability, and succeed by empowering those closest to the action to make critical decisions. Let’s look at what the history and practices of military and law enforcement organizations can teach us about building agile, resilient teams.
The U.S. Army operates a dedicated Mission Command Center of Excellence that trains leaders in decentralized, agile decision-making—a core characteristic of successful Scrum teams.
Military and Law Enforcement
Many agile and scrum experts appreciate agile principles and the scrum framework because of their experience in the military. Military organizations are mistakenly perceived to value strong centralized decision-making, often called command-and-control. However, military strategists have long known that centralized decision-making leads to defeat on the battlefield. A commander can’t possibly see all parts of the battlefield or communicate fast enough to understand a chaotic, rapidly changing situation or exploit fleeting opportunities. Wise commanders understand that they must empower those at all levels to make timely decisions.
Command-and-control actually refers to a command being given (a strategic vision or goal for an operation), but control and autonomy for completing the mission are delegated to those executing the plan.
Military organizations are strictly hierarchical and rely on top-down orders at all times.
The most effective military leaders empower those at every level to make decisions, especially in fast-changing situations.
Reflect: In your experience, where have you seen centralized control slow down decision-making or reduce effectiveness on a team?
Turning the ship around
In 1999, U.S. Navy Captain David Marquet became commander of the USS Santa Fe, a submarine for which he had no training. The crew was trained to do what they were told. The submarine and crew were the lowest-performing in the fleet at the time. It was a deadly combination.
Captain Marquet’s first orders to his new crew were to do something he didn’t know the submarine was incapable of doing, yet the crew answered with “Yes, sir.” But nothing happened. The crew had been immersed in a top-down culture of “Do what I say.” It became clear to the new captain that the crew’s culture would not work well with a captain trained on another type of ship.
Captain Marquet spent his time from that moment changing the culture of the USS Santa Fe from top-down to a “leader-leader” model. Instead of the crew coming to the captain and asking, “Requesting permission to submerge the ship,” Marquet required the crew to come to him, saying, “Captain, I intend to submerge the ship. All men are below. Hatches are shut. Ship is rigged for dive. Bottom depth checked. We’re in the water that’s been assigned to us.” The captain responded, “Very well.”
With an assurance of technical competence of the crew and the clarity of purpose he gave them, Captain Marquet empowered his crew with psychological ownership to be effective, self-managing, and cross-functional to determine the right thing to do through continuous feedback. He turned the submarine from the worst to the most successful, and since his retirement, the submarine has continued to win awards for excellence.
A leadership approach where authority and responsibility are distributed, empowering team members to act as leaders within their role.
Research in organizational psychology shows that teams with decentralized decision-making react faster and perform better in uncertain environments. By distributing authority, teams increase resilience, speed of response, and innovative problem-solving—key traits in both military operations and agile Scrum teams.
How could the “I intend to…” approach change the way your current team operates?
Special forces
Special operations forces, also called special forces, are uniquely trained to be adaptable, self-reliant, and operate in uncertainty. In the U.S., special forces refer to notable teams like the Green Berets and Navy Seals.
In many ways, agile teams are analogous to special-forces teams. Both types of teams are small, highly trained, highly professional, cohesive, and cross-functional. Special-forces teams are small and cross-functional, so they can adapt to situations that arise. Cross-functionality means that every team member can do more than one thing; ideally, every team member can do every skill necessary.
Like agile teams, special-forces teams are stable and long-lived. Through hard-earned experience, their members know how to work together and trust one another, and they pitch in to do whatever is needed to accomplish the mission. That mission may require fluency in a foreign language, building relationships with local villagers, or even skilled use of deadly force if necessary. The mission may call for any combination of those things, yet carrying out the mission may involve something completely different. Special-forces teams know how to inspect and adapt.
Also, both agile and special-forces teams create a sense of mutual accountability. In high-stakes situations, whether in business or on the battlefield, the desire not to let a team member down is more important than any deadline.
Like scrum sprints, missions for military teams are normally broken down to be accomplished quickly, within weeks at the longest. Longer missions wear out soldiers, deplete supplies, and require significant ongoing support. You find an exponential correlation between the length of a mission and the cost and rate of failure. Short missions provide better focus, team morale, and success.
One of many examples in which a military commander succeeded by changing his command-and-control approach is Admiral Nelson at Trafalgar. Instead of requiring strict adherence to signal flags hoisted on his flagship, Nelson delegated substantial authority to ship captains, saying, “In case signals can neither be seen or perfectly understood, no captain can do very wrong if he places his ship alongside that of the enemy.”
A group in which every member can perform multiple roles or skills, enabling the team to adapt rapidly to changing situations.
Many technology companies model their agile teams after special-forces units, emphasizing small size, versatility, and mission focus to tackle complex, unpredictable challenges.
- Military organizations succeed by decentralizing decision-making.
- Special forces and Scrum teams share agile, cross-functional practices.
Scrum and the FBI
Cyberattacks of all sorts are increasing worldwide, from credit card hacking to government and military security threats. Military and cyberwarfare experts agree that controlling this expanding threat is a major concern. As a result, cyberthreat deterrence programs that can adapt to the ever-changing nature of these sophisticated challenges are needed — and needed fast. In many cases, it’s an issue of national security.
The FBI has been increasingly active in finding response solutions to these cyberattacks on a national and criminal level. However, leadership knows it isn’t enough to use old techniques for handling these uber-modern threats. New ways of applying technology, shaping their workforce, and collaborating with partners are required.
Not surprisingly, they’re approaching this conundrum with scrum.
After the 9/11 terrorist attacks, the FBI began to work on streamlining its flow of information and coordination with all relevant entities. After a couple of false starts, it developed the Sentinel program: a comprehensive software case management system. The goal is to replace a current system consisting of a mixture of digital and paper information flow with a purely digital one.
For ten years, the project was conducted using the FBI’s prescribed waterfall methods, including extensive upfront design and fixed requirements. A new CIO, Chad Fulgham, started requiring incremental delivery from the contracted developers. Here are some of the symptoms of the waterfall process used up to that point:
- Only 4 of 18 workflows were live but with defects.
- Less than 1 percent of the 14,000+ forms were created in the new system.
- Cost to date was $405 million, with …
“No battle plan survives contact with the enemy.”
Helmuth von Moltke (the Elder)Switching from traditional project management to Scrum helped the FBI respond more effectively to modern cyber threats, emphasizing the value of adaptability and rapid iteration in high-stakes environments.
Think of a time when a project you were involved with faced unexpected changes. How could Scrum’s incremental approach have made a difference?
Experience the power of decentralized decision-making.
- With your current team, choose a routine task that is usually assigned top-down.
- Instead of issuing instructions, ask team members to state their intent (“I intend to…”) and propose their own plan of action.
- Observe and discuss how this shift affects ownership, engagement, and the quality of decisions.
What is mission command?
Tap to revealA military doctrine where leaders set strategic goals but empower subordinates to make decisions on how to achieve them.
What is a cross-functional team?
Tap to revealA team in which members have multiple skills and can support different roles, increasing adaptability and resilience.
How does the “leader-leader” model differ from traditional leadership?
Tap to revealIt distributes authority and responsibility, encouraging everyone to act as a leader rather than following orders passively.
Describe a real or hypothetical scenario where decentralized decision-making could improve your team’s performance. How would you implement this, and what challenges do you foresee?
Which leadership approach did Captain David Marquet implement on the USS Santa Fe to transform its performance?
The most effective teams—whether in the military or business—embrace decentralized decision-making, enabling adaptability, ownership, and mission success even in uncertain environments.
Cross-functional, empowered teams inspired by special-forces models are more resilient and capable of overcoming rapidly changing challenges.
What lessons from military or law enforcement practices could most benefit your current team or organization, and why?
How confident are you that you can explain how military principles like mission command apply to Scrum teams?