WORKFORCE
field of expertise, they each have unique insights that they are eager to apply.
By employing a learning-by-doing process, the Army Software Factory allows cohort members to tackle real-world Army chal- lenges while simultaneously honing their software development skills. Anyone in the Army can submit a problem set for consideration through a portal available on the Army Software Factory website. If selected, a problem set will be assigned to a cohort member project team—supported by embedded software development expert trainers, who have experience working with leading tech companies—that will work on that problem set as a software application.
As cohort members progress in the program,
they have the opportunity
to focus on Agile and Lean Six Sigma management, user-centered design and various application and platform engi- neering disciplines. Te Army Software Factory additionally keeps its members apprised of emerging trends in software, cybersecurity and cloud technologies through regular professional development sessions delivered by thought-provoking tech leaders and subject matter experts.
Tese activities are pivotal because they show cohort members and potential cohort members that, rather than needing to leave the Army to become software developers, they can grow professionally in a compet- itive field while staying in uniform (or while maintaining DA civilian status, as the case may be).
Te Army Software Factory also holds promise for alleviating Army reliance on outside software development and troubleshooting support. Increased self- sufficiency will likely prove essential in future operational environments, where communications may be disconnected
NO PAYNE NO GAIN
Chief Warrant Officer 2 Rob Payne at the Army Software Factory. Before joining the Software Factory, Payne made a basic application for operators in his motor pool to digitize the maintenance process, which proved useful for his Soldiers, and underscored the benefits of having Soldiers participate directly in the digital tool development processes. (Photo by Army Futures Command)
or dispersed across multiple domains. In such settings, having Soldiers capable of applying software development skills to remedy software problems that may arise will provide an important warfighting advantage.
ARMY INGENUITY Te strength and beauty of the system also lies in its ability to harness domain expertise present in participating Soldiers and DA civilians, many of whom already have years of Army service. An example of this is the story of Chief Warrant Offi- cer 2 Rob Payne.
Payne enlisted as a Bradley Fighting Vehicle mechanic in 2008 and became a
warrant officer to have a more direct role in improving processes and influencing maintenance operations.
He did just that by making the preven- tative maintenance checks and services process—a system of ensuring mission readiness by tracking and performing preventive maintenance on trucks and other rolling stock equipment—easier for Soldiers.
As Payne became more familiar with the Global Combat Support System – Army, he realized that maintainers were taking digital system output but using a pen-and- paper process to get updated preventative maintenance information back into the
https://
asc.ar my.mil 133
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 |
Page 133 |
Page 134 |
Page 135 |
Page 136 |
Page 137 |
Page 138 |
Page 139 |
Page 140 |
Page 141 |
Page 142 |
Page 143 |
Page 144 |
Page 145 |
Page 146 |
Page 147 |
Page 148
