Software Acquisition

AAF  >  Software Acquisition  >  Develop Strategies

Reference Source: DODI 5000.87 Section 3.3.b.(6)

 

Programs will continuously improve or refine software development processes, practices, tools, and program strategies to reflect them.

Reference Source: USD(A&S) Guidance

FY20 NDAA Section 800 directs Software Acquisition Pathway programs are not to be treated as MDAPs. Further, the Adaptive Acquisition Framework transformed the policies, processes, and culture to: empower PMs; delegate decisions; tailor in processes; and focus on data driven decisions. This context provides PMs freedom to tailor the AAF in accordance with their Decision Authorities’ direction which can impact acquisition reporting requirements (statute and policy).

Strategic intent. The SWP is intended to balance speed with rigor. It values working software over comprehensive documentation, but requires proper planning and coordination of strategies and designs commensurate with size and risk. Documentation isn’t developed for compliance purposes to pass the next milestone (as there are none in the SWP), but rather to proceed with managed risk and continuous improvement throughout development.

The risk of providing an information requirements checklist is the potential unintended consequence of reducing the creative compliance mindset of the DoD.  DoD is very contextual – we have the largest, most diverse software ecosystem and portfolio on Earth.  The PM and PEOs have the flexibility to tailor in processes and documents based on the unique needs of their portfolio, as opposed to a universal standard.  This reduces bureaucratic overhead and red tape that limits agility, and drives cost and schedule duration increases.

Principles based framework:

What follows is a draft framework to guide services and PEOs on expectations for tailoring-in processes and information-needs/documents for DODI 5000.87.  Ultimately, a review of statutory requirements applicability by the Service and OSD OGC must confirm which statutes and MDAP requirements do not apply, given the MDAP treatment prohibition from FY20 NDAA Section 800, included here:

Statutory Requirements: The Software Pathway intent is to reduce bureaucracy to maximize taxpayer investment and accelerate capability to our Warfighters.  In turn, the intent is to reduce the documentation requirements and focus the program’s efforts on planning and producing working software to enable rapid and continuous delivery. It is recognized that there are some statutory and regulatory information requirements that must be met such as a Component cost position, cybersecurity strategy, or bandwidth requirements review. (Note: a hybrid pathway adoption may require statutory requirements for associated hardware of the parent program). However, we take the view that many of the statutory requirements are information requirements that can be included in the Acquisition Strategy and not as stand-alone documents. (The team has not assessed the distinction between application and embedded software acquisition/pathway use wherein certain safety requirements may apply; e.g., nuclear surety.)

Regulatory Requirements: Regulatory documents should be developed only if deemed essential to program execution.  Some document content will be combined.  Many regulatory information requirements are covered in the CNS, User Agreement, Acquisition Strategy, and Cost Estimates.  Some regulatory information may still be required on a case by case basis, based on capabilities being delivered (e.g., waveform assessment if delivering new or modified signal formats). Decision Authorities as have discretion in the regulatory arena on what to require and when to require it.

The buttons below provide further details on the core strategy documents for the Software Acquisition Pathway.

The tables below provide an initial pass on statutory and regulatory information requirements for Programs using the Software Acquisition Pathway

Continuous Learning Modules

• Introduction to Agile Software Acquisition
• Introduction to DoD Software Lifecycle Management
• Practical Software and Systems Management
• Software Acquisition for the Program Office Workforce
• Continuous Process Improvement

Program Management Resources

• 10 Commandments for Software, Defense Innovation Board
• Detecting Agile BS, Defense Innovation Board
• Dos and Don’ts for Software, Defense Innovation Board
• Metrics for Software Development, Defense Innovation Board
• Software Acquisition Practice Study, Defense Innovation Board
• Continuous Iterative Development (Agile) Measurement Framework, PSM
• 7 Traits of High Performing Acquisition Teams, DAU
• Changing Software Acquisition in DoD, DAU