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
$ FIGURE 1


Te agile development methodology, an alternative to traditional project man- agement, actively engages stakeholders throughout the development process. Created in the 1970s, the agile meth- odology features


iterative development


and adaptation, in contrast with some of government’s old ways of developing technology, most notably the waterfall approach of sequential development.


“Having a close working relationship with our product owners has paid big dividends for us,”


said LTC Delisa Hernandez, PM AcqBusiness.


Under normal conditions, AcqBusi- ness supports one enhancement release each month,


coupled with weekly


maintenance releases. To enable the organization to respond quickly to the needs of external stakeholders, program officials tailored processes to permit time-sensitive releases, following a pre- defined rather than an ad hoc process. Tus the AcqBusiness team is confident of sufficient oversight and willing to embrace time-sensitive releases.


ARMY ACQUISITION DASHBOARD In October 2012, the Hon. Heidi Shyu, assistant secretary of the Army for acquisition,


DASHBOARD SCREEN SHOTS


The AAD provides information on multiple program parameters for ASA(ALT) leadership, acquisition program managers and other authorized personnel. (SOURCE: PM AcqBusiness)


logistics and technol-


ogy (ASA(ALT)) and Army acquisition executive (AAE), received a briefing on the AAD, with positive results. Doug Wiltsie, milestone decision authority for AcqBusiness and the Program Execu tive Officer Enterprise Information Sys- tems (PEO EIS), granted permission for AcqBusiness to proceed with the initial operating capability for AAD.


With AAD’s initial release, all ACAT I data for Defense Acquisition Executive Summary reporting of Army programs were made available to AAD end users.


ASA(ALT) is formulating a policy and timeline to extend data reporting to other Army programs. Te ultimate goal is to conduct Army program reviews from the AAD rather than from manu- ally generated PowerPoint slides.


Currently, the AAD is live. (See Figure 1.) With the release of AcqBiz 3.2.4 in March, several enhancements were implemented, including:


 AAD account approvals—User access requests to the AAD are now reviewed and approved by PEO organization account managers.


 ACAT II and III data—Te AAE and PEOs now have a holistic view of their ACAT I, II and III program data across the ASA(ALT)


enterprise. Adding


ACAT II and III data to the AAD ana- lytic environment allows for monthly program status reviews (PSRs) on these programs via the AAD.


 PSR—PEO and ASA(ALT) leader- ship can now brief from the AAD. Te PSR tab in the PEO Dashboard section launches a separate window that con- tains all relevant information necessary for the PSR and promotes consistent views across programs


to acquisition community senior leadership. ASC.ARMY.MIL 83


EFFICIENCIES


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  |  Page 177  |  Page 178  |  Page 179  |  Page 180  |  Page 181  |  Page 182  |  Page 183  |  Page 184  |  Page 185  |  Page 186  |  Page 187  |  Page 188  |  Page 189  |  Page 190  |  Page 191  |  Page 192  |  Page 193  |  Page 194  |  Page 195  |  Page 196