1. JTAMS PRE-CDR IT/SIS ANALYSIS
19 October FY 3
PM JTAMS / PM JUGGERNAUT
Student Name:
Student Name:
PM JTAMS Lead
PM JUGGERNAUT Lead
Presentation Intro/Overview
Measures Assessment
Data Rights Analysis
Award Fee Criteria Analysis (JTAMS)
Presentation Intro/Overview
Software Development Planning
Key Software-related Questions for CDR
MRES Risk Assessment
PRACTICUM 3
Note: P1 and P2 we are Milestone centric and P3 is CDR focused.
Student Instructions:
Each team will develop the practicum solution slide package using the templated slides provided, the given scenario/artifacts –additional info is in the Job Aids folder.
All slides will be submitted to the instructors electronically (Blackboard/Shared Drive) and hard copy (printed 2 slides per page and double sided)
Each team will designate a PM’s to present the results of the analysis prepared by the team.
You will have 1.5 hours for research and development of the practicum solution. The PM and Deputy PM will have 5 minutes to present their designated slides.
Summary – Are We Ready for CDR? (Joint Brief)

2. JTAMS MEASURES ASSESSMENT
Summarize your analysis
Worksheet #2
Problems: Summarize the problems in the areas of: JRATS External Interfaces; JTAMS Subsystem Interfaces; Rgmnts Volatility; Defects by Priority
Impacts: Describe the root causes and assess the potential impacts. Include the implications for Software Quality.
PRACTICUM 3
See: Job Aids - Practicum 3 JRATS_JTAMS Measures
Instructions:
1.Review the set of measures and identify issues.
2.Do an integrated analysis. Perform a causal analysis to identify root causes and underlying problems. Provide a summary for the two or three major issues, describing the problems, impacts, risks, potential outcomes, and alternatives. Document your analysis on Worksheet #2.
Alternatives
Describe the alternative courses of action you would recommend for this project.

3. Real-time Engine Data Rights Analysis#
COA
Cost ($)
Schedule DR
(R, GP, U)
Risk and Risk level
(L, M, H) 1
Challenge the V-Robotics assertion (do nothing) 2
Negotiate for Government Purpose Rights 3
Develop the Real-time software engine to support MRES 4
Accept Juggernaut’s assertion and agree to the limited rights associated 5
Allow another contractor to do the work 6
(Student Provided COA – required)
Which option is the best from a Government perspective and why?
Which option is best from Juggernaut’s perspective and why?
Which option is your recommended option and why?
PRACTICUM 3
See: Scenario and Artifact; full contract is also in Job Aids
Instructions: Identify and assess COA’s for addressing the data rights issue - for the real-time engine. You are required to develop another COA – row 6 on the slide.
There is data in the contract that can give you cost and schedule impacts for some of the COA’s - estimate or use the H/M/L approach if you do not have cost or schedule information
Do not just identify risk as H/M/L – explain the factors that went into your risk assessment – what is the risk, etc?
Use the lesson material from lesson 16 and any references for that lesson to understand “Restricted Rights” “Government Purpose Rights” and “Unlimited Rights”:
Identify the risks the Government might incur – for instance:
Schedule and Cost risk of acquiring data rights versus cost risk of not acquiring data rights
Assess the risks to the program and to the acquiring Service/Agency of not acquiring the desired product data or data rights due to cost or other considerations.
Explore alternatives for acquiring the needed data rights for life cycle support from the OEM.
Determine if, by not acquiring the data and rights, the program has locked the Government into a course of action that would be costly or impossible to change at a later date.

4. Award Fee Criteria Analysis (JTAMS)
Award Fee Weights For Period 1
(25 Jun FY2 After SRR)
6.1 Risk Management = .5
Why?
6.2 Configuration Management = .2
6.3 Interface Control =
6.4 Formal Inspections =
6.5? =
Award Fee Weights For Period 2 (16 Nov FY3 After PDR)
6.1 Risk Management =
Why?
6.2 Configuration Management =
Why?)
6.3 Interface Control =
6.4 Formal Inspections =
6.5? =
PRACTICUM 3
NOTE: PM Juggernaut was provided the Contract modification that added our Five Award Fee Areas
See: Artifact – full contract is in job aids - SEE JTAMS CONTRACT, SECTION H.6; AWARD FEE DETERMINATION
We have awarded a Cost-Plus-Award-Fee (CPAF) contract to JUGGERNAUT (See Job Aids) for the JTAMS effort. Using the contract, task 2 is to: (1) identify the Government Software Quality Performance Statement (Goals of Program); (2) given Section H and Section H.6.1 Risk Management Award Fee Determination (AFD) as an example, determine the Award Fee Area for Section H.6.2, H.6.3, and H.6.4 based on the criteria listed; (3) for Section H.6.5, you come up with your own Award Fee Area based on the Government Software Quality Goals; (4) Fill in the Award fee table weights for Contract Performance Period 1 (some already completed) and Contract Performance Period 2 and explain why you gave the areas the weights you did. See Contract in Job Aids.

5. JTAMS PRE-CDR IT/SIS ANALYSIS
19 October FY 3
PM JTAMS / PM JUGGERNAUT
PM JTAMS Lead
PM JUGGERNAUT Lead
Presentation Intro/Overview
Measures Assessment
Data Rights Analysis
Award Fee Criteria Analysis (JTAMS)
Presentation Intro/Overview
Software Development Planning
Key Software-related Questions for CDR
MRES Risk Assessment
PRACTICUM 3
Note: P1 and P2 we are Milestone centric and P3 is CDR focused.
Summary – Are We Ready for CDR? (Joint Brief)

6. Software Development Plan
Identify the purpose and who produces the Software Development Plan. (SDP)
Provide an overview of AMRU’s approach to software development:
Explain AMRU’s expected benefits or rationale for using this approach
What concerns does V-Robotics have concerning their subcontractor AMRU?
PRACTICUM 3
See: Scenario and Artifacts

7. Key Software-Related Questions for CDR
Management metrics relevant to life cycle phase: (Latest Cost Estimate)
CDR Question
Answer and Discussion
Has the software cost estimate been updated based upon actual measured project software development performance and productivity to date? If not, what are the implications?
Has cost of acquiring, licensing and configuring COTS and / or GOTS computer hardware and software been considered? Was this included in the original estimate? Identify any implications
What caused (or could be the cause of) a change in the software cost since the beginning of the project, if any? (based on the current scenario)
PRACTICUM 3
See: Job Aids\DoD CDR Checklist SW Only - NOTE: Apply the questions identified to the JTAMS scenario. You may have to refer back to the cost estimating portions of Practicums 1 and 2. See the Cost Factor Cheat sheet (used in Lesson 3) for review of cost factors.

8. Question 4 (MRES Risk Assessment)
Description of Risks
Question 4 (MRES Risk Assessment)
Using the risk management cube methodology, identify 2 risks to JTAMS as a result of AMRU's software development approach.
Likelihood / Consequence Assessment
Risk 2
Risk 1
Risk 1
If-Then Stmt:
Likelihood/Consequence Justification:
Risk 1
Risk 2
Risk 2
If-Then Stmt:
Likelihood/Consequence Justification:
Likelihood
Consequence
Likelihood
Consequence
PRACTICUM 3
See: scenario and artifacts The intent is identify some potential risks and explain the rationale for the risk assessments on the risk cube. “Potential programmatic concerns/risks” in the artifacts

9. Summary – Are We Ready for CDR?
Completion of the CDR should provide the following:
(1) An established system initial product baseline
Status:
(2) An updated risk assessment for EMD
(3) An updated CARD (or CARD-like document) based on the system product baseline
(4) An updated program development schedule
(5) An approved Life-cycle Sustainment Plan
Government and Juggernaut Assessment:
Are we ready for CDR?
PRACTICUM 3
– (JOINT TASK GOV + CONTRACTOR) For this point in the development effort: Summarize our readiness for CDR. Read the Student Situation