The pathway objective is to facilitate rapid and iterative delivery of software capability to the user. This pathway integrates modern software development practice such as Agile Software …

SWP values working software over comprehensive documentation but requires proper planning and coordination of strategies and designs commensurate with size and risk.

Dated October 2, 2020 In accordance with the authority in DoD Directive 5135.02, this issuance establishes policy, assigns responsibilities, and prescribes procedures for the establishment of software acquisition pathways to provide for the efficient and effective acquisition, development, integration, and timely delivery of secure software in ...

The software acquisition pathway is for the timely acquisition of custom software capabilities developed for the DoD. Software programs that meet the definition of a covered Defense Business System (DBS) should use the DBS pathway in accordance with DoDI 5000.75 but may elect to incorporate this pathway for custom developed software.

The Software Acquisition Pathway (SWP) enables organizations to execute rapid and iterative delivery of software capabilities by using modern software development practices and active user...

This SWP quick start primer is to assist acquisition professionals in using the Software Acquisition Pathway. It provides the core items needed to enter the Planning Phase and quickly move into the Execution Phase.

Congress directed the DoD to establish a separate and distinct Software Acquisition Pathway in the FY20 National Defense Authorization Act, also known as Section 800 authorities.

The software acquisition pathway is for the timely acquisition of custom software capabilities developed for the DoD. Software programs that meet the definition of a covered Defense Business System (DBS) should use the DBS pathway in accordance with DoDI 5000.75 but may elect to incorporate this pathway for custom developed software.

Agreement between the operational and acquisition communities to ensure active user involvement and informed decision making. Overall program champion from an operational, requirements, and resourcing perspective. Ensures active user engagement, shapes roadmaps and backlogs, and measures value.

Acquisition Policy: Develop strategies and methods to enable evolving software acquisition, modernization, sustainment (A/M/S) policy Acquisition Practice: Speed the insertion & adoption of new technology & methods into A/M/S programs