Software Acquisition Pathway (SWP)

The Software Acquisition Pathway (SWP) is DoD's pathway under 10 U.S.C. 3603 and DoDI 5000.87 for iterative software delivery: a minimum viable capability release within one year of first obligation, updates at least annually, and no JCIDS or MDAP treatment.

The SWP runs two paths — applications software on commercial hardware and cloud platforms, and embedded software in weapon systems. A planning phase produces a capability needs statement, a user agreement, an acquisition strategy, and a cost estimate; execution then iterates with agile methods and DevSecOps rather than milestone reviews.

The schedule discipline is statutory. Programs must demonstrate viability and effectiveness for operational use within one year of first obligating funds (the minimum viable capability release), then deliver new capability at least annually. SWP programs are not treated as major defense acquisition programs regardless of cost. A March 2025 Secretary of Defense memo made SWP the preferred pathway for DoD software development, with CSOs and Other Transactions the default award approaches.

The miss is treating the pathway as relief from rigor. The one-year MVCR clock starts at obligation, and the user agreement commits real operator time; programs that staff neither drift back onto a traditional schedule with none of the pathway's benefit.

Regulatory Reference

10 U.S.C. 3603; DoDI 5000.87

RFO Status

SWP lives in Title 10 and DoD policy, which the FAR Overhaul's deviations do not rewrite; current change comes instead from the FY 2025 NDAA codification at 10 U.S.C. 3603 and the March 2025 software acquisition memo.

Category

Programs & Pathways

How AcqBot Helps

AcqBot drafts the SWP planning artifacts — capability needs statement, user agreement, and acquisition strategy — to DoDI 5000.87's content requirements and flags when a CSO or Other Transaction is the directed award approach under the March 2025 memo.