1. AMRU Release 2 Release Report
30 October FY 03
Rusty Prentiss

2. Contents Release Plan within Larger JTAMS Integrated Master Schedule
AMRU 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 2: Cumulative Flow Diagram
Burn Up / Burn Down charts
Story Aging Graphic for Release 2: Histogram
Summary of Progress

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

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

5. Risks Likelihood 1 2 3 4 5 Consequence Likelihood 1 2 3 4 5
Number: FY02-1
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 V-Robotics and PMO staff
Number: FY02-13
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.
Likelihood
Consequence
Likelihood
Consequence

6. MRU Block 1 Implementation Progress
Based on the AMRU STIM Release 2 report, cut and paste the measurement visualization that provides a holistic picture of AMRU’s development progress. Add in vertical lines that mark Release 1 and Release 2 from AMRU.
Note on the chart when AMRU stopped waiting for the mobility data and started working mobility based on their assumptions.

7. How to Read Cumulative Flow Diagram
The Cumulative Flow Diagram (CFD) uses an area graph to chart the transition of items from one state to another. The states that are summarized here (within our Agile management tools there are more states than summarized here for use at the team level)
Readywe have converted the requirements received from V-Robotics into epics and stories, and their value has been estimated as story points
Dev (Development)the work represented by those story points is actively being coded and unit tested
Testthe work represented by the story points is in integration test and regression tests (the automated ones within MRU; not the manual ones at the integration lab)
Ready for V-Roboticssoftware and related compliance documentation is ready to be delivered to V-Robotics upon request and is available to all authorized stakeholders within the MRU sandbox area (contact Margaret Wilson for access permission). At minimum, software is delivered to V-Robotics at the completion of the Block.
The sum of Dev and Test is the work being conducted at any given time.
Looking horizontally, you can see the cycle time of stories across the time span, both holistically and for each state
Looking vertically, you can see the amount of work that is in different parts of the life cycle at any particular time

8. Block 1 Burn Down

9. Block 1 Burn Up

10. How to Read Burn-down and Burn-up Charts
A burn down chart is a graphical representation of showing the amount of work remaining on a vertical and a timeline on a horizontal axis.
If the tasks increase during a sprint at the same rate as the team completes them, a burn-down chart will give the impression that no work was performed. This is the reason burn down charts are typically used for internal team management and not shared outside the sprint team.
A burn-up chart shows how much work was actually accomplished (as opposed to how much work remains to be completed) and how much total work the project contains.
Burn-up charts are extremely useful to understand team progress even if the scope changes.

11. Story Aging AMRU Release 2
Note to V-Robotics: the 20 story points represented by >9 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.

12. How to read the Story Aging Histogram
There are six categories that indicate how long the story was in the “Ready” state without being worked.
Stories that have been in the Ready state for >2 releases may be candidates for removal from the backlog if the reason they have aged is that they don’t have sufficient value
For stories that have been in the Ready state for >1 release due to external information that is not available, the issue should be raised to a management level that can help to resolve the issue
AMRU uses a template for characterizing the value and complexity of the item for items that have to raised to higher levels of technical and/or business management

13. Summary
Block 1 implementation is on schedule. The remaining items in the backlog are associated with later Blocks.
With the exception of the JCCS information related to Mobility, the information needed to implement the STIM model have been available, even if not always timely.
We have begun using “best available info” for the Mobility aspects of the model. We are concerned that, if our assumptions are incorrect, we may have to rework part of the model to correct the data we have used.
Impact on the architecture and schedule for this kind of rework is unknown at this time
Juggernaut and V-Robotics staff were engaged and helpful in both the Release 1 and Release 2 demonstrations. We are pleased that early implementation of the UAV data has helped V-Robotics to refine their designs and interfaces.