Adaptive Acquisition Framework (AAF)

The Adaptive Acquisition Framework (AAF) is the Department of Defense's modernized acquisition policy, implemented through DoD Instruction 5000.02 and related policies, that replaced the previous one-size-fits-all acquisition model with six distinct pathways tailored to different program types and urgency levels.

What is the Adaptive Acquisition Framework?

The AAF was established to address criticism that DoD's legacy acquisition process was inflexible and applied the same oversight and documentation requirements to a $500 million software update as to a $20 billion aircraft carrier program. The six AAF pathways are: (1) Urgent Capability Acquisition for immediate warfighter needs; (2) Middle Tier of Acquisition for programs that can prototype or field within five years; (3) Major Capability Acquisition for large-scale development programs (traditional MDAPs); (4) Software Acquisition for software-intensive programs using Agile delivery; (5) Defense Business Systems for enterprise IT and ERP systems; and (6) Acquisition of Services for services contracts. Each pathway has its own tailored policies, oversight requirements, and decision points appropriate to the program type. Program managers select the pathway best suited to their program's technology maturity, urgency, cost, and delivery model. The AAF also encourages hybrid approaches, a program might begin with MTA for rapid prototyping and transition to Major Capability Acquisition for full production.

Why AAF matters for government contractors

The AAF directly affects which acquisition regulations, contracting mechanisms, and oversight requirements apply to programs a contractor is pursuing. Software companies benefit from the Software Acquisition Pathway's agile emphasis. Startups benefit from the MTA pathway's OTA-compatible structure. Understanding which AAF pathway a target program uses helps contractors tailor their proposals, pricing, and development approach appropriately.

Example

A cybersecurity software company is supporting a program office that is deciding which AAF pathway to use for a new endpoint security platform. The program office chooses the Software Acquisition Pathway, committing to Agile development cycles, continuous delivery, and government-accessible software repositories. The contractor structures its proposal around sprint planning, DevSecOps practices, and government access to the software backlog, all required under the Software Acquisition Pathway policy.

Frequently Asked Questions

Which AAF pathway replaced the traditional JCIDS/PPBE/DAS framework?

The Major Capability Acquisition pathway most directly corresponds to the traditional acquisition model (with Milestone A, B, C and capability-based requirements). The other pathways provide alternatives for programs that do not fit the traditional model. The AAF as a whole reflects DoD's recognition that the traditional JCIDS/DAS framework is too rigid for the full range of defense acquisition needs.

Can a program switch pathways after it starts?

Yes. The AAF explicitly anticipates that programs may need to change pathways as they mature or as circumstances change. A program might begin as Urgent Capability Acquisition, transition to MTA for expanded development, and eventually enter Major Capability Acquisition for full-rate production. Pathway decisions are reviewed at key program milestones.

What is the Software Acquisition Pathway and why is it significant?

The Software Acquisition Pathway (established by Section 800 of the NDAA FY2020) creates a dedicated framework for software-intensive programs using Agile and iterative delivery. It allows continuous software delivery, reduces documentation burden, and enables government access to software source code and development tools. It represents a fundamental shift in how DoD acquires software compared to traditional waterfall programs.

Who decides which AAF pathway a program uses?

The program's Milestone Decision Authority (MDA), working with the program manager and acquisition strategy team, selects the appropriate AAF pathway based on the program's characteristics. Pathway selection is documented in the Acquisition Strategy, which must be approved by the MDA before significant contracting actions proceed.