AGILE ACQUISITION FOR ... HARDWARE?
Direct user feedback and communications throughout this development cycle is critical for success.
the product development process. It may or may not be a fielded product,” as defined in my 2022 research presentation to the Naval Postgraduate School, “Minimum Viable Product as an Engineering Strategy for Urgent Needs Acquisition: A Case of the High Mobility Decontamination System.”
Tis definition is inclusive of both hardware and software functional prototypes developed as early as possible in the devel- opment cycle. It enables iterative prototype development to add new features and agility to address new or changing requirements.
A TEMPLATE FOR USING MVP IN HARDWARE DEVELOPMENT Both the High Mobility Decontamination System and the Nega- tively Pressurized Conex followed an agile approach to hardware development as described in the diagram on Page 99. Tis hybrid approach uses an MVP strategy and feedback loops that are the centerpiece of the Software Acquisition Pathway but tailored to hardware acquisition. Tis process emphasizes direct user feedback throughout requirements analysis and prototype devel- opment. In the cases of NPC and HMDS, the programs tailored the iterative MVP approach to Urgent Capability Acquisition. A short requirements analysis phase derived performance require- ments from Joint Urgent Operational Needs Statements through an engage, derive, assess and document loop with collaborative end user and combat developer involvement. Tese requirements led to a review with the milestone decision authority (MDA) to approve a sound acquisition strategy, sign key documents, assign funding and green light the contracting strategy.
Both the NPC and the HMDS used other transaction agreements for contracting. Tese agreements are prototype-centric and enable the MVP engineering approach. Because requirements will not be well defined for agile and iterative prototyping programs, the acquisition and contracting strategies must include “sprint- like” development structures. Considering the rigor involved with modifying hardware, iterations are not true sprints as used in soft- ware development that last for one to two weeks. Tese hardware “sprint-like” iterations may last for several weeks or even months
100 Army AL&T Magazine Spring 2024
in order to address the redesign or delivery of parts, installa- tion of modifications, or the availability of test fixtures. Both the acquisition and contracting strategies should take these consid- erations into account.
Once in the iterative prototyping phase, the MVP (labeled as P(1) in the diagram) undergoes a design, develop, demonstrate and analyze feedback loop with direct user and combat devel- oper involvement. Te design and development portions of the loop should prioritize schedule over other metrics, as the goal of the MVP is to understand the utility of the capability with the least amount of effort conducted. “Demonstrate” actions include simultaneous developmental or laboratory testing and user eval- uations in a test-analyze-fix-test cycle. Direct user feedback and communications throughout this development cycle is critical for success. Te program managers must work with the end users and combat developers to prioritize and reprioritize requirements and feature demands based on a consistent flow of new information in the “analyze” action. Design decisions are often made on the spot to keep the test-analyze-fix-test cycle flowing.
At the completion of the development and demonstration of the MVP, the program will undergo an iteration decision process, typically executed with the MDA, program manager, user deci- sion maker and other relevant senior leaders. Based on the information gathered during the MVP development sprint, senior leaders will make a “go/no-go” decision. A “go” decision allows the program to proceed. A “no-go” decision leads to program
DEFINING MVP AND MVC
MINIMUM VIABLE PRODUCT (MVP) The MVP is a prototype that provides the program office with enough information to determine if the urgent need acquisition is worthwhile as soon as possible in the product development process. It may or may not be a fielded product.
MINIMUM VIABLE CAPABILITY (MVC) Like an MVP, the MVC is the first iteration that is ready for fielding. It enables the user to meet mission needs with the minimum amount of effort in development. The MVC is both an operational and learning tool for future iterations.
Page 1 |
Page 2 |
Page 3 |
Page 4 |
Page 5 |
Page 6 |
Page 7 |
Page 8 |
Page 9 |
Page 10 |
Page 11 |
Page 12 |
Page 13 |
Page 14 |
Page 15 |
Page 16 |
Page 17 |
Page 18 |
Page 19 |
Page 20 |
Page 21 |
Page 22 |
Page 23 |
Page 24 |
Page 25 |
Page 26 |
Page 27 |
Page 28 |
Page 29 |
Page 30 |
Page 31 |
Page 32 |
Page 33 |
Page 34 |
Page 35 |
Page 36 |
Page 37 |
Page 38 |
Page 39 |
Page 40 |
Page 41 |
Page 42 |
Page 43 |
Page 44 |
Page 45 |
Page 46 |
Page 47 |
Page 48 |
Page 49 |
Page 50 |
Page 51 |
Page 52 |
Page 53 |
Page 54 |
Page 55 |
Page 56 |
Page 57 |
Page 58 |
Page 59 |
Page 60 |
Page 61 |
Page 62 |
Page 63 |
Page 64 |
Page 65 |
Page 66 |
Page 67 |
Page 68 |
Page 69 |
Page 70 |
Page 71 |
Page 72 |
Page 73 |
Page 74 |
Page 75 |
Page 76 |
Page 77 |
Page 78 |
Page 79 |
Page 80 |
Page 81 |
Page 82 |
Page 83 |
Page 84 |
Page 85 |
Page 86 |
Page 87 |
Page 88 |
Page 89 |
Page 90 |
Page 91 |
Page 92 |
Page 93 |
Page 94 |
Page 95 |
Page 96 |
Page 97 |
Page 98 |
Page 99 |
Page 100 |
Page 101 |
Page 102 |
Page 103 |
Page 104 |
Page 105 |
Page 106 |
Page 107 |
Page 108 |
Page 109 |
Page 110 |
Page 111 |
Page 112 |
Page 113 |
Page 114 |
Page 115 |
Page 116 |
Page 117 |
Page 118 |
Page 119 |
Page 120 |
Page 121 |
Page 122 |
Page 123 |
Page 124
