AMRU Release 4 Release Report 30 May FY

AMRU Release 4 Release Report 30 May FY 03 Rusty Prentiss

Contents • Release Plan within Larger JTAMS Integrated Master Schedule • MRU Release/Block Plan: • Releases 1 & 2 make up Block 1 • Release 2 & 3 & 4 = Block 2 • Release 5 = Block 3 • • • Risks Progress Graphic for Release 4: Cumulative Flow Diagram Burn Up / Burn Down charts Story Aging Graphic for Release 4: Histogram Defect Closure Summary of Progress

Joint Training and Maintenance System (JTAMS) Increment 1 Government Roadmap Schedule Showing STIM (in green) TODAY is 30 May FY 3 FY 00 FY 01 MDD MSA Milestones & Phases TECH DEV TD TD ITR ASR SRR FY 05 FY 06 Post CDR Assessment FY 07 FY 08 PROD & DEPLOYMENT MS C FRP IOC DECISION JTAMS-1 IOC EMD SSR PDR CDR Block 1 MRU Development Prototype Testing Development Testing EOA (Prototypes / EDMs) FCA PRR Block 3 Block 2 EDMs DT&E Operational Testing Deliveries FY 04 Engineering and Manufactuing Demonstration EMD TD Contract Award FY 03 MS B MS A Final RFP Release Technical Reviews FY 02 OA LFT&E IOT&E

MRU S/W Release Schedule TODAY is 30 May 03 FY 02 Q 1 Q 2 FY 03 Q 4 PDR AMRU Milestones MRU on contract Q 1 Q 2 Q 4 CDR PDR 1 Q 3 2 3 OA 4 5 Block 1 complete STIM S/W Release

Risks Number: FY 02 -1 Likelihood Risk: STIM will be the first involvement with an agile development approach for V-Robotics (and for the government program office Impact: A lot of time may be required to explain our process and how we fit in to the bigger acquisition picture Mitigation Strat: Offer training to key VRobotics and PMO staff 1 2 3 4 5 Consequence Number: FY 03 -6 Likelihood Risk: AMRU’s reputation within the simulation community may be harmed if we don’t deliver as promised Impact: Existing contracts may be cancelled, difficult to win new contracts Mitigation Strat: Spread the blame beyond AMRU. Reinforce we had to make assumptions to be so efficient at all meetings 1 2 3 4 Consequence 5

Risks Number: FY 03 -7 Likelihood Risk: Block 2 may not be completed by release 4 Impact: Impact to V-Robotics schedule Mitigation Strat: Release Block 2 and 3 at the same time 1 2 3 4 5 Consequence Number: FY 02 -13 Likelihood Risk: OBD interfaces specs have not been provided to AMRU Impact: Re-work may be needed if assumptions prove to be wrong – should have minimal schedule impact Mitigation Strat: Postpone Firebird and JUGV as long as possible. Assume interfaces will be same as on Global Hawk. 1 2 3 4 Consequence 5

MRU Block 2 Implementation Progress

Block 2 Burn Down Release 3 & 4 470 410 370 Tasks Remaining 320 290 250 220 215 210 170 11 12 13 14 15 Sprint 16 17 18 19 20

Block 2 Burn Up Release 3 & 4 560 470 470 470 560 470 Tasks 470 560 300 255 260 17 18 19 220 180 150 100 60 30 11 12 13 14 15 Sprint Ready for V-Robotics 16 Block 1 Tasks 20

Defect Closure Defects Since Block 1 140 120 100 80 60 40 20 0 Sprint 11 Sprint 12 Sprint 13 Sprint 14 Sprint 15 Cumulative Opened Sprint 16 Cumulative Closed Sprint 17 Sprint 18 Sprint 19 Sprint 20

Story Aging AMRU Release 4 Story Aging 120 100 80 70 70 70 60 40 30 20 < 1 sprint 20 1 -3 sprints 3 -5 sprints 5 -7 sprints 7 -9 sprints 9 -11 sprints >11 sprints Note to V-Robotics: the 20 story points represented by >11 sprints category all relate to JCCS interface information that is needed for MRU to work the Mobility aspect of the model. We have proceeded without this data based on best information available. This introduces a risk of later rework.

Summary • Block 2 implementation is delayed. • We used “best available info” for the Mobility aspects of the model. Our assumptions were incorrect, as a result we will have to rework part of the model to correct the data we have used. • Impact on the architecture is limited to the MIM and Weather Module. • Block 2 capability can be included along with Block 3 in release 5.