Software program engineering strategies proceed to evolve and enhance, with SEI analysis enjoying a key position in serving to the Division of Protection (DoD) achieve the advantages of those enhancements and drive modifications to revolutionize software program acquisition. Our work helps simplify guidelines, adapt practices to allow decisive actions, enhance workforce functionality, and speed up adoption of economic and scientific improvements. Since its inception, the SEI has been main the DoD’s embrace of trendy software program engineering strategies, resembling Agile and DevSecOps. The SEI contributed its experience to the event of the Software program Acquisition Pathway (SWP), which was issued in 2020 as Division of Protection Instruction 5000.87. The coverage departed from many years of rules geared towards {hardware} acquisition by encouraging these trendy software program practices to streamline the event and acquisition of software-enabled methods to ship capabilities on the velocity of ever-changing mission wants.
The discharge of Secretary of Protection Pete Hegseth’s March 6 memo, Directing Fashionable Software program Acquisition to Maximize Lethality, launched a brand new crucial that DoD packages should improve and speed up their adoption of the SWP as the popular path for software program acquisition. The March 2025 memo goals to scale up SWP successes throughout all the Protection Division to hurry, streamline, and safe the event and supply of software-driven mission capabilities, from the again workplace to the entrance traces. As we define on this put up, this concentrate on the SWP has been the catalyst behind our efforts to develop a new assortment of instruments to assist DoD packages adapt their acquisition practices to speed up software program supply.
A Transient Introduction to the Software program Acquisition Pathway
In contrast to prior generations of acquisition coverage, the SWP is designed for software-intensive methods. Its goal is “to facilitate fast and iterative supply of software program functionality to the person.” The SWP emphasizes trendy, iterative software program growth strategies, automated tooling (together with automated testing and cybersecurity testing), and energetic person engagement to ship software program capabilities on the velocity of want and allow customers to adapt to altering situations. Determine 1 under reveals the iterative nature of engagement between customers, program workplaces, and product groups below the SWP.
Implementing the SWP: 5 Vital Questions
Prior to now 5 years our SEI group of software program acquisition consultants has collaborated extensively with DoD program groups and coverage homeowners to implement the SWP in numerous contexts, establish boundaries and challenges, and monitor outcomes. In the middle of that work, we have now recognized frequent questions and obstacles that packages encounter as they undertake the SWP. Addressing these questions usually warrants extra instruments and sources to allow groups to place their SWP packages for fulfillment.
The most typical questions we encounter about launching SWP packages embrace
- Are we actually able to undertake the SWP? Coming into the SWP Planning part requires a signed Acquisition Resolution Memorandum (ADM) and draft Functionality Wants Assertion (CNS). However there’s much more to being adequately organized and geared up for the profitable execution of an SWP effort. It’s not sufficient, for instance, for this system’s product group to simply do Agile. Program groups usually don’t have expertise implementing trendy software program growth approaches and want to realize an understanding of what these approaches imply in observe.
- What’s a Functionality Wants Assertion (CNS), and the way precisely can we develop one that matches our state of affairs? Many customers and program workplace groups wrestle to shift from a Functionality Improvement Doc (CDD) articulation of must crafting a CNS on the acceptable stage. This wrestle usually ends in a CNS that’s merely CDD content material that has been copied and pasted into the CNS template. The up-front stage of funding within the specificity required to create a CDD runs counter to the flexibleness and flexibility the SWP is designed to allow. An acceptable CNS supplies the correct stage of element to allow the wanted flexibility.
- How can we assess progress and establish dangers early sufficient to make corrections and stop points? Program groups usually study a slip in a supply date or value overrun too late to do something about it. Even when groups overview metrics supplied by their product group, these issues aren’t obvious. Engineering knowledge is a strategic asset, and efficient metrics packages have to allow program groups to grasp how technical metrics drive actual mission worth.
- How can we construct a sturdy person settlement (UA) and join it to worth assessments (VAs)? A UA is an important handshake that explicitly hyperlinks the event of capabilities to real-world warfighter outcomes, and VAs present suggestions and return on funding knowledge on the worth delivered. Typically, UAs are applied on the flawed stage (too far faraway from the day-to-day work of customers), or they don’t sufficiently take into account several types of finish customers who’ve a stake within the functionality being delivered.
- How can we scope and sequence a minimal viable product (MVP), minimal viable functionality launch (MVCR), and subsequent releases? Many program groups wrestle with successfully defining and scoping an MVP and MVCR, resulting in misaligned expectations between this system group and stakeholder teams (e.g., warfighters, certifiers, testers).
Answering these 5 important questions constitutes the bedrock essential to attain profitable SWP acquisitions. Getting them proper is difficult work. Luckily, program groups don’t have to go it alone.
Introducing the Software program Acquisition Go Bag
It’s a fact amongst warfighters that step one in finishing a mission is dependent upon the load they keep on their again. On the SEI a key tenet of our work focuses on equipping the warfighter with the correct gear for his or her mission wants. With that in thoughts, the SEI publicizes the launch of the Software program Acquisition Go Bag.
The Go Bag will characteristic an extensible assortment of tailorable kits that program groups can use to allow the supply of software program capabilities on the velocity of want. Every equipment accommodates instruments and strategies for executing and implementing the weather of your software program program. Every equipment accommodates Tactical Guides on matters resembling collaborating with stakeholders, acquiring and leveraging the correct knowledge, managing expectations, stopping (or recovering from!) frequent pitfalls, and measuring what issues to remain on target.
The primary equipment to be launched is the SWP Necessities Equipment, which can embrace the primary three Tactical Guides:
- SWP: Prepared, Set, Go! supplies a mechanism for assessing the mission’s readiness to undertake the SWP, figuring out any shortfalls, and acquiring the sources, info, and help wanted for fulfillment.
- Cracking the CNS Code delivers a methodology for making use of the overall steering of the SWP to particular packages and tasks with their very own distinctive aims, constraints, and challenges.
- Pack Mild, Measure Proper accommodates steering for packages to develop and constantly apply significant measures of progress, high quality, sources, and worth to their SWP program.
Suggestions from early customers will assist us to prioritize matters to handle within the subsequent set of Tactical Guides:
- Constructing a Worth-Oriented Consumer Settlement will supply a scientific strategy that packages can use for figuring out user-community members and explaining their position, affect, and anticipated commitments. This strategy permits packages to explicitly combine negotiated VAs, primarily based on user-community enter, into this system’s measurement plan.
- MVP, MVCR, and Launch Planning will clarify strategies that packages can use to get from growing a CNS to delivering an MVP and MVCR, together with dealing with non-capability objects (e.g., behaviors of interfacing methods, high quality attributes resembling maintainability).
Go Bag belongings can be launched iteratively as we establish and prioritize wants with stakeholders and obtain your suggestions. Each few weeks, we are going to launch a brand new Tactical Information and host a companion webcast. As we work with program groups, we may also usually replace the Go Bag with new kits, supplemental instruments, templates, and extra—all primarily based on confirmed profitable practices. Click on right here to learn of recent releases and updates in software growth.
Go Baggage aren’t only for packages on the SWP, both. Our SEI group has helped a whole lot of DoD packages ship software-enabled functionality by means of our distinctive integration of data-driven insights, software program engineering analysis, and acquisition science. We’re packing that have into the Go Bag so program groups can implement confirmed practices to drive profitable outcomes.
The (Software program Acquisition) Pathway Forward
To kick off the launch of the Software program Acquisition Go Bag, we’re internet hosting a stay webcast on October 22. Be a part of us to study extra about this effort and share your ideas on the Go Bag Necessities Equipment. Over the approaching weeks, we are going to announce the discharge of every new Tactical Information and host an related webcast about each through the Go Bag announcement mailing checklist.
