FIGURE 2 Collect Metrics


Step 1 Ide


Step 2


dentify adjust func


software build.il are


nctions for eachac so


fy/adjust ma s fo


ajojor


Receieceive story point (breakdown of major functions) backlog for -day spri


reak nc


s) ac


ajo fo


the 30-day sprint. Step 3 Execute th


xecute the 30-day spri sprint.


Step 4


p 4 Recei ewo


eceive working code (source and


executables) and


so rce an ut bl


nd completed story points.


Release code (First seven days of sprint)


Analysis (Two weeks)


Collect Metrics


(Source: CMDS Project Office, Ranjit Mann, Laura Brezinski - Graphic Designer) STEP BY STEP


This image details the six stages of Agile software development, beginning with identifying the functions for each build and ending with testing and integration. (SOURCE: Ranjit Mann and Laura Brezinski, CMDS Project Office)


Checkout (One week)


Collect Metrics


Step 5


p 5


Perform st amic


rform static and dynamic IV&V.


nd


Step 6 p 6 Integrat an rate and test. st.


Repeat Step 1


R


function (Step 1). Tis


function was decomposed into user


stories by major end item (MEI) (e.g., command-and-control node, launcher, interceptor) and provided to the product office (Step 2). Te developer applied the user stories to develop the executable code during the 30-day sprint cycle (Step 3). Te MEI developer delivered this executable code, which imple- mented the launcher-connection functionality, to the product office (Step 4). Next, the SIV&V team performed dynamic and static analysis to verify and validate the launcher-connection functionality (Step 5). Finally, the IFPC Inc 2-1 product office integrated and tested the executable software from MEI devel- opers, and communication between the launcher and command and control node was proven in the System of Systems Inte- gration Lab (SoSIL) by the IFPC Inc 2-I Product Office. Te SWIPT collected the metrics and provided them to the product office and each MEI developer in Steps 3, 5 and 6.


RISK REDUCTION Software development is a primary program risk for IFPC Inc 2-I. Early defect detection, using Agile processes, reduced the need for rework and decreased software risk.


Te SWIPT maintains the schedule with functioning software verified monthly. Te SWIPT also monitors the performance with each sprint release by verifying functionality planned in the backlog (i.e., user stories). Tis approach ensures that the final software meets performance requirements while maintain- ing cost and schedule. Te SWIPT estimates that the IFPC Inc 2-I program saved more than 2,000 hours in software rework by using Agile processes, which resulted in $400,000 in cost savings during a six-month software build. Tis savings was realized when a message format issue was discovered while implementing the launcher-connection functionality.


ASC.ARMY.MIL 61


ACQUISITION


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  |  Page 197  |  Page 198  |  Page 199  |  Page 200  |  Page 201  |  Page 202  |  Page 203  |  Page 204  |  Page 205  |  Page 206  |  Page 207  |  Page 208