Army announces new policy to drive adoption of agile software development practices (2024)

Evolving technology is changing the nature of warfare. Software has transformed from a means of operating hardware-based weapons systems to being the essential driver of nearly all the Army's weapons, business, and training platforms. The Army must be able to rapidly develop and upgrade these software-based capabilities to maintain a competitive advantage. To meet this challenge, the Army recently announced a new policy changing its approach to software development.

The new policy institutionalizes modern software development approaches across the Army, in line with industry best practices. These approaches – which include agile and lean practices – focus on iterative development and delivery of software in close coordination with users. This type of development allows software to be rapidly developed and refined over time, accelerating the Army’s ability to deliver needed capabilities to soldiers.

“We’re learning from current conflicts — including in Ukraine — that the Army’s success on future battlefields will depend on our ability to rapidly update software and disseminate it to the operational force,” said Secretary of the Army Christine Wormuth. “Software development must be a source of our military advantage and the Army’s new software policy will ensure we have the right processes in place to inject innovation quickly and achieve a digital transformation of our warfighting capabilities.”

“Our traditional approach to software is no longer meeting the demands of our warfighters,” said Gabe Camarillo, Under Secretary of the Army. “This policy represents a significant effort to comprehensively adjust our legacy software development processes in line with private sector best practices. These changes will fundamentally reshape how we develop and acquire software, making us more agile and innovative.”

To accelerate adoption of these modern approaches, the policy reforms many of the institutional processes that underpin the software development lifecycle, which have historically been cumbersome and time intensive. This includes changing the way requirements for software systems are written, the types of acquisition strategies and buying models employed, and how the Army writes its requests for proposals and contracts with vendors. It also streamlines and modernizes the test and evaluation activities required, and changes how these solutions are assessed for cyber vulnerabilities. Lastly, it modifies the way cost estimates for agile software solutions are developed and how these systems are supported and maintained over time. As talent is a key driver for success, the policy also includes several initiatives focused on developing the talent and expertise needed to execute modern software development.

The reforms these institutional processes through a series of targeted reform initiatives, which can be summarized by five key changes:

1.Changing the Way Requirements Are Written: Software requirements will be captured in concise, high level needs statements in place of the detailed, prescriptive requirements documents used in the past. In line with industry best practices, soldiers will be continuously involved throughout the process to ensure solutions are refined over time consistent with user needs.

2.Employing Flexible Acquisition and Contracting Strategies: Acquisition and contracting strategies for software development efforts will provide the ability to quickly adapt to changing requirements. This includes maximizing use of the Software Acquisition Pathway, which is tailored for rapid and iterative delivery consistent with industry practices; employing flexible contracting strategies such as modular contracting; and using the appropriate contract types that allow for refinement of the requirements as the software evolves and user needs change.

3.Streamlining and Modernizing Key Processes: Traditional, manual processes associated with software development and deployment will be streamlined and modernized to reduce the time and resources required to deliver software. This includes reducing duplicative test requirements and streamlining cybersecurity processes, including the process to achieve authority to operate on Army networks.

4.Adopting a New Sustainment Model: Software-based systems will no longer follow the traditional process in which a system transitions to sustainment once development is complete. In line with industry best practices, these systems will instead plan for continuous improvement and development over the entirety of the lifecycle. This change recognizes that modern software development is never complete.

5.Developing Talent & Expertise: Personnel trained in various aspects of modern software development practices will be made available to assist Army organizations in the implementation of modern software development practices. This includes establishment of the Digital Capabilities Contracting Center of Excellence at Aberdeen Proving Ground to improve and streamline contracting processes for software development efforts. And the establishment of the Software Management and Response Team, a centralized team of software development experts at Army Headquarters, to provide expertise and support to software efforts planned across the enterprise. Simultaneously, the Army will explore ways to more broadly attract, retain, and train personnel skilled in modern development.

The policy goes into effect immediately. As best practices in software development continue to evolve, the Army will adapt its guidance, as appropriate.

Army announces new policy to drive adoption of agile software development practices (2024)

FAQs

Does the military use agile methodology? ›

Army announces new policy to drive adoption of agile software development practices. Evolving technology is changing the nature of warfare. Software has transformed from a means of operating hardware-based weapons systems to being the essential driver of nearly all the Army's weapons, business, and training platforms.

What are the 6 phases of agile software development? ›

The Agile software development life cycle is the structured series of stages that a product goes through as it moves from beginning to end. It contains six phases: concept, inception, iteration, release, maintenance, and retirement.

What are the five states of the agile life cycle? ›

The 5 stages of the Agile software development lifecycle
  • Stage 1: Ideation. All successful Agile software development projects begin with an ideation stage. ...
  • Stage 2: Development. ...
  • Stage 3: Testing. ...
  • Stage 4: Deployment. ...
  • Stage 5: Operations. ...
  • Methodology. ...
  • Architecture. ...
  • Automation.
Apr 10, 2024

Is Agile development still a thing? ›

It's a simple set of principles that still have weight. The 2022 State of Agile report found that 70% of agile practitioners are satisfied with these practices and that they most appreciate the increase in cross-company collaboration and continuous improvement they drive.

What is the purpose of DoD in Agile? ›

The DoD is a set of high-level criteria for determining if a product increment is complete. It applies to all product increments and defines the overall quality of a product. In contrast, acceptance criteria are low-level conditions that apply only to specific user stories or features.

What does IT mean to be Agile in the military? ›

'Agility' is a Military Word

Each of these tenets is interesting in its own right, but we're focusing on Agility. The military definition of 'Agility' is unsurprising: Agility is adapting to, and exploiting, the chaos of the battlefield, and the goal is to do it faster and better than your enemy does.

What is the difference between Agile and Scrum? ›

In Agile methodology, software is delivered on a regular basis for feedback, whereas in Scrum methodology, software is delivered after each sprint of development. Agile and Scrum share similar methods like collaborative iterations, and for a good reason: Scrum is an Agile approach.

What is an example of Agile methodology? ›

The most popular and common examples are Scrum, eXtreme Programming (XP), Feature Driven Development (FDD), Dynamic Systems Development Method (DSDM), Adaptive Software Development (ASD), Crystal, and Lean Software Development (LSD).

What are the 4 agile development methodologies? ›

Agile development methodology

There are many different forms of the agile development method, including scrum, crystal, extreme programming (XP), and feature-driven development (FDD).

What is Agile in simple terms? ›

Agile isn't defined by a set of ceremonies or specific development techniques. Rather, agile is a group of methodologies that demonstrate a commitment to tight feedback cycles and continuous improvement.

What is the 3 5 3 rule in Agile? ›

The Scrum Framework is simple, and it follows the 3-5-3 structure: 3 Roles, 5 events, 3 Artifacts. These elements are crucial to the success of doing Scrum and nothing is optional.

What is the difference between Agile and waterfall? ›

Flexibility: Agile encourages teams to respond quickly and adaptively to changes during the development process. Waterfall is less flexible and resistant to change once the project's scope has been defined. Testing: Testing is essential to the agile and waterfall methodologies, but the approaches differ significantly.

Is agile still relevant in 2024? ›

In 2024 and beyond, we can expect further evolution in these frameworks, including greater integration with emerging technologies like AI and DevOps, emphasis on continuous learning and improvement, remote collaboration tools and a focus on building a strong Agile culture within organizations.

Is scrum losing popularity? ›

Scrum is one of the most popular Agile methods/frameworks for project management that has helped countless teams improve and achieve better efficiency. However, the framework has started to lose popularity as some teams discover other approaches work better for them.

Why are companies moving away from agile? ›

Agile development is fading in popularity at large enterprises - and developer burnout is a key factor. Agile development methodology is facing significant obstacles as the tech industry goes through a wave of changes including developer burnout, shifting working environments, and the rise of AI.

Does the government use Agile? ›

In September 2020, the Government Accountability Office (GAO) released its draft of The GAO Agile Assessment Guide: Best Practices for Agile Adoption and Implementation for government programs using Agile practices.

What is an example of Agile methodology being used? ›

Examples of Agile Methodology. The most popular and common examples are Scrum, eXtreme Programming (XP), Feature Driven Development (FDD), Dynamic Systems Development Method (DSDM), Adaptive Software Development (ASD), Crystal, and Lean Software Development (LSD). Teams generally pick one or two methods.

What are the three Army planning methodologies? ›

Methodologies that assist commanders and staffs with planning include Army design methodology, the military decisionmaking process (MDMP), and troop leading procedures.

Top Articles
Latest Posts
Article information

Author: Clemencia Bogisich Ret

Last Updated:

Views: 5999

Rating: 5 / 5 (60 voted)

Reviews: 83% of readers found this page helpful

Author information

Name: Clemencia Bogisich Ret

Birthday: 2001-07-17

Address: Suite 794 53887 Geri Spring, West Cristentown, KY 54855

Phone: +5934435460663

Job: Central Hospitality Director

Hobby: Yoga, Electronics, Rafting, Lockpicking, Inline skating, Puzzles, scrapbook

Introduction: My name is Clemencia Bogisich Ret, I am a super, outstanding, graceful, friendly, vast, comfortable, agreeable person who loves writing and wants to share my knowledge and understanding with you.