AGILE APPLICATION IN MATERIEL ACQUISITION
through Army and joint interoperability certification. Interoperability certifica- tion is the process of confirming that the system can successfully exchange crit- ical information while interfacing on a network. IFMC is part of the working group currently evolving the modern- ization efforts for Army interoperability certification. Te Digital Transformation Technologies Directorate for the deputy assistant secretary of the Army for data, engineering and software is leading the undertaking and including stakeholders in the process. Tis partnership ensures the modernized interoperability certification aligns with the Army’s transformation.
An Agile approach is needed to adapt test- ing methodologies and standard operating procedures to accommodate the swift pace of continuous verification and validation of capabilities, compliance and security. Te flexibility of using an Agile framework eliminates bottlenecks and optimizes the value stream of delivery to facilitate shorter feedback cycles. Tis will result in even quicker delivery in a continuously improv- ing cycle.
AGILE MATERIEL RELEASE Te Army materiel release process is a critical stage in the development of new equipment. Te purpose of this process is to ensure that Army equipment is safe, meets operational requirements and is logistically supportable before it is released to warfighters. Tis process provides Army leadership with the control and visibility necessary to ensure that items intended for issue have been thoroughly evaluated and approved for use. Currently, materiel release is a sequential development process that requires completion of each phase before the next one begins. Tis approach depends on the deliverables of the previ- ous phase and corresponds to a rigid set of requirements. Regulatory guide- lines governing current materiel-release processes do not align with the pace of fielding and delivering capabilities.
In fiscal year 2022, IFMC identified the need to adapt the materiel release process to enable system-of-systems capability releases in line with Agile development. An Agile approach would allow for more frequent adaptation of requirements as
new capabilities are fielded, delivered and integrated. Te intent is to have a more flexible materiel release that can be incre- mentally improved as more information about system utilization becomes available post-deployment.
IFMC launched the Agile materiel release working group in coordination with the Office of the Assistant Secretary of the Army for Acquisition, Logistics and Technology to adapt the existing materiel release process to keep up with the rapid software capabilities deliveries needed in the field. Te goal is to develop a new system-of-systems Agile materiel release process that will enable annual deliv- ery of capability to critical systems. Te challenge is to define a process that will provide the flexibility to enable a solution that is tailorable and scalable for a task force commander, while ensuring materiel provides a safe, suitable and sustainable capability.
IBCS hardware and software are being produced more quickly and efficiently by involving stakeholders in the development
AGILE IN EVERYTHING
The Integrated Fires Mission Command Project Office implements Agile methodology throughout the acquisition process.
44
Army AL&T Magazine
Spring 2023
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 |
Page 125 |
Page 126 |
Page 127 |
Page 128 |
Page 129 |
Page 130 |
Page 131 |
Page 132
