search.noResults

search.searching

dataCollection.invalidEmail
note.createNoteMessage

search.noResults

search.searching

orderForm.title

orderForm.productCode
orderForm.description
orderForm.quantity
orderForm.itemPrice
orderForm.price
orderForm.totalPrice
orderForm.deliveryDetails.billingAddress
orderForm.deliveryDetails.deliveryAddress
orderForm.noItems
BEEN THERE, DONE THAT


FIGURE 1


Tere is a longstanding and continuing trend of acquisition programs failing to achieve acquisition program baseline (APB) goals; that is to say, program man- agers often fail to meet important cost, schedule and performance aspects of the plans they agreed on with their superiors. Te Government Accountability Office (GAO), formerly the General Accounting Office, has documented this trend thor- oughly in multiple reports.


Given that defense acquisition is and will remain multifaceted, imperfect and evolving, must its future be completely and irremediably bleak? I suppose the an- swer to this question depends on whom you ask. Our government watchdog or- ganizations, particularly GAO, can point to many examples of management mis- takes. If you look at the three metrics of every program—cost, schedule and per- formance—you will see that over several decades, many acquisition programs have missed or will miss achieving APB goals in one or all three of these metrics.


Put another way, lots of defense programs cost more than they should, arrive late or don’t do what they’re supposed to. GAO detailed this situation in its 2015 and 2016 annual reports “Defense Acquisi- tions: Assessments of Selected Weapon Programs,” which rate specific programs on the attainment of “product knowledge” and describe program status in terms of cost, schedule, performance and risk.


Sometimes PMs sign up for cost or sched- ule goals that are unachievable; in Octo- ber 2015, GAO characterized this as a systemic problem in which the acquisi- tion process is “in equilibrium,” mean- ing that new programs are initiated with slender chances of completion on sched- ule and within cost. In many programs, technologies have not been ready to sup- port mature, production-ready systems,


140


THE TIME WASN’T RIGHT


One key lesson learned from big programs that have run into difficulty: Major technology development needs to happen before any system designed around it goes into production. These four programs were hampered by still-developing technologies that were nevertheless built into the program’s design; when those technologies did not pan out as expected, the programs suffered. (SOURCE: Michael W. Boudreau, Col., USA (Ret.))


leading to schedule concurrency—for example, simultaneously redesigning, retesting and manufacturing—which of- ten brings delays, cost increases and then more delays. It is easy to paint a dismal picture of defense acquisition.


THE BLEAK From my perspective, the elephant in the room is DOD’s propensity to launch


“mega” programs that are beyond its ability to manage successfully. Te de- partment’s really large programs, such


Army AL&T Magazine


January-March 2017


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  |  Page 149  |  Page 150  |  Page 151  |  Page 152  |  Page 153  |  Page 154  |  Page 155  |  Page 156  |  Page 157  |  Page 158  |  Page 159  |  Page 160  |  Page 161  |  Page 162  |  Page 163  |  Page 164  |  Page 165  |  Page 166  |  Page 167  |  Page 168  |  Page 169  |  Page 170  |  Page 171  |  Page 172  |  Page 173  |  Page 174  |  Page 175  |  Page 176