1. ISA 201 Intermediate Information Systems Acquisition

2. Lesson 17 Practicum 3

3. Today you will learn to (1 of 2):
Given a DoD acquisition scenario, asses required aspects of DoD SE technical reviews, technical processes, and technical management processes.
Given a DoD acquisition scenario, apply System Engineering Lessons Learned and Best Practices when dealing with software.
Apply the five components of the DoD Risk Management Process Model to a given IT acquisition scenario
Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset.
Given a DoD acquisition scenario, apply laws and DoD directives to ensure successful IT systems management throughout the acquisition life cycle.
Given an IT acquisition scenario, identify the most appropriate software methodology (or a combination of methodologies) to meet the expectations of the government.
Identify the key principles of an agile software development process
Given an acquisition scenario, identify key issues with using agile software development processes in a DoD environment
Practicum 3

4. Today you will learn to (2 of 2):
Given an IT acquisition scenario, assess the components of the contractor’s Software Development Plan (SDP).
Given an IT acquisition scenario, apply the measurement results to support IT program decisions.
Given a scenario, identify program IT decision information requirements.
Create a set of program IT measures that are linked to the program decision information requirements.
Given an IT acquisition scenario, recommend an incentive structure.
Given an IT acquisition scenario analyze different types of data rights
Given a software acquisition scenario, recognize the preferred method for identifying and tracking defects
Given acquisition scenarios with several software-reliant program issues, analyze how each issue may affect achieving the program's software quality objectives
Practicum 3

5. Systems Acquisition Activities Review
Lesson Plan
Systems Acquisition Activities Review
JTAMS Update
Marching Orders
Practicum 3
March 2014

6. Engineering and Manufacturing Development
PURPOSE: to develop, build, and test a product
to verify that all operational and derived requirements have been met and to support production
or deployment decisions
ENTER: Adequate Risk Reduction; Approved Requirements; Full Funding in FYDP
ACTIVITIES: Complete detailed design, system-level CDR, integrated testing, establish product baseline, demonstrate manufacturing processes and supportability
COMPLETION: the design is stable and the system meets validated capability requirements demonstrated by developmental and initial operational testing as required in the TEMP; the system has met or exceeds all directed EMD Phase exit criteria and Milestone C entrance criteria
Practicum 3

7. MDA Approves: Milestone C
Updated Acquisition Strategy and Acquisition Program Baseline
Entry into LRIP for systems that require LRIP, production or procurement for systems that do not require LRIP, or limited deployment for MAIS programs or software intensive systems with no production components
Exit criteria for LRIP if appropriate
Acquisition Decision Memorandum
Practicum 3 7

8. JTAMS Update Lesson Plan Status Systems Acquisition Activities Review
Marching Orders
Practicum 3
March 2014

9. JRATS and JTAMS Update
Joint Reconnaissance and Targeting System (JRATS)
Congrats, we passed Milestone B!
Please see the Milestone B ADM in your Job Aids.
We are now getting ready for CDR Milestone C.
Our Focus will be on understanding the requirements and risks of a pre-CDR JTAMS.
You will analyze our JTAMS contract (WALK THE CONTRACT)
SECTION C is the Statement of Work (SOW).
SECTION H is the Award Fee Criteria.
SECTION J is the Contracts Data Requirements List (CDRL). and Work Breakdown Structure (WBS)
Identify risks.
Build an Award Fee Plan.
Build a Metrics Management Program with your contractor.
Practicum 3 9

10. Practicum 3 Timeline
Practicum 3 10 10

11. Joint Training and Maintenance System (JTAMS) Increment 1 Government Roadmap Schedule
Practicum 3 11

12. Marching Orders Lesson Plan Status
Systems Acquisition Activities Review
JTAMS Update
Marching Orders
Practicum 3
March 2014

13. Practicum 3 Instructions
Each team will develop the practicum solution slide package using the templated slides provided, the given scenario and the artifacts, and 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 JTAMS and PM JUGGERNAUT to present the results of the analysis prepared by the team. (See Student Template)
You will have 1.5 hours for research and development of the practicum solution. The PM JTAMS and PM JUGGERNAUT will have a maximum of 5 minutes to present their designated slides.
Practicum 3
March 2014 13

14. Scope of Presentation Summary – Are We Ready for CDR? (Joint Brief)
During this exercise, each team will be required to perform Level II Information Technology/Software Acquisition Management tasks that would typically be conducted in a government program office.
PM JTAMS
PM JUGGERNAUT
Presentation Intro/Overview
Key Software-related Questions for CDR
Measures Assessment
Data Rights Analysis
Award Fee Criteria Analysis (JTAMS)
Juggernaut’s Award Fee Analysis
Software Development Planning
AMRU’s Development Approach
MRES Risk Assessment
MRES Measures Assessment
Summary – Are We Ready for CDR? (Joint Brief)
All slides will be submitted to the instructors electronically (Blackboard/Shared Drive) and hard copy (printed 2 slides per page and double sided)
See the file “Practicum 3 Situation and applicable artifacts”
See the Student Template Slides for the practicum requirements
Practicum 3

15. Marching Orders
Remember, you are members of the PM JTAMS and PM JUGGERNAUT – you must select a PM for each.
Go to your Student CD and open the folder for this Practicum.
See the file “Practicum 3 Situation and applicable artifacts”
Time
Event
Misc
Practicum Intro
Instructor
Research and prepare analysis*
Student teams
1450
Submit entire analysis
Submit electronically on BB or shared drive AND hard copy
Student PM/DPM Presentations
Students present slides by team IAW the slide templates
Instructor Wrap up
*Ensure you allow time for the presenters to prepare
Practicum 3
March 2014 15

16. Today we learned to (1 of 2):
Given a DoD acquisition scenario, asses required aspects of DoD SE technical reviews, technical processes, and technical management processes.
Given a DoD acquisition scenario, apply System Engineering Lessons Learned and Best Practices when dealing with software.
Apply the five components of the DoD Risk Management Process Model to a given IT acquisition scenario
Given a description of an IT acquisition need, assess documentation to ensure specific information provides a clear understanding of the intended IT acquisition objectives from program outset.
Given a DoD acquisition scenario, apply laws and DoD directives to ensure successful IT systems management throughout the acquisition life cycle.
Given an IT acquisition scenario, identify the most appropriate software methodology (or a combination of methodologies) to meet the expectations of the government.
Identify the key principles of an agile software development process
Given an acquisition scenario, identify key issues with using agile software development processes in a DoD environment
Practicum 3

17. Today we learned to (2 of 2):
Given an IT acquisition scenario, assess the components of the contractor’s Software Development Plan (SDP).
Given an IT acquisition scenario, apply the measurement results to support IT program decisions.
Given a scenario, identify program IT decision information requirements.
Create a set of program IT measures that are linked to the program decision information requirements.
Given an IT acquisition scenario, recommend an incentive structure.
Given an IT acquisition scenario analyze different types of data rights
Given a software acquisition scenario, recognize the preferred method for identifying and tracking defects
Given acquisition scenarios with several software-reliant program issues, analyze how each issue may affect achieving the program's software quality objectives
Practicum 3