1. ISA 201 Intermediate Information Systems Acquisition

2. Lesson 20 Practicum 4

3. Today you will learn to (1 of 2):
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
Given an IT acquisition scenario, apply the measurement results to support IT program decisions.
Assess set of program IT measures that are linked to the program decision information requirements.
Practicum 4 Introduction

4. Today you will learn to (2 of 2):
Apply the measurement results to support IT program decisions.
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
Given a Department of Defense (DoD) Information Technology (IT) acquisition scenario, apply the principles of Continuous Process Improvement (CPI) to evaluate a vendor’s potential to deliver quality software products within cost and schedule parameters
Identify relevant considerations that influence the acquisition lifecycle of a software-reliant system.
Identify the criteria necessary for transitioning to sustainment.
Given a specific DOD IT acquisition scenario, appraise secure data archiving and storage practices.
Identify areas that must be transitioned from the development environment to the sustainment environment
Analyze software sustainment planning considerations.
Recognize the five essential characteristics of a cloud service.
Describe the problems with Legacy software applications and Cloud.
Summarize some Program concerns when purchasing cloud services from a vendor.
Recognize public, private, community and hybrid cloud deployment models (NIST).
Practicum 4 Introduction

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

6. Production and Deployment
ENTER: Acceptable performance in Developmental Testing (DT) & Operational assessment (OA); mature software; no significant manufacturing risks; approved Capabilities Production Document (CPD); acceptable interoperability and operational supportability; demonstration of affordability; fully funded
ACTIVITIES: Low Rate Initial Production, Initial Operational Test and Evaluation (IOT&E), and interoperability testing of production-representative articles; Full-Rate Production (FRP) Decision; fielding and support of fielded systems; Initial Operational Capability (IOC)/ Full Operational Capability (FOC)
EXIT: Full operational capability; deployment complete
PURPOSE:
to produce and
deliver requirements-compliant products to receiving military organizations
Practicum 4 Introduction

7. Operations and Support
ENTER: Approved CPD; approved Life Cycle sustainment Plan (LCSP); successful FRP Decision ACTIVITIES: LCSP implementation; Performance-Based Life-Cycle Product Support (PBL) planning, development, implementation, and management; initiate system modifications as necessary; continuing reviews of sustainment strategies, Demilitarize and dispose of systems IAW legal and regulatory requirements, particularly environmental considerations and explosives safety
PURPOSE:
Execute a support program that meets materiel readiness and operational support performance requirements, and sustains the system in the most cost-effective manner over its total life cycle.
Practicum 4 Introduction

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

9. JRATS and JTAMS Update
JTAMS and JRATS passed their CDRs! The MDA indicated some continuing concern with the interface definitions that remain to be addressed. These will continue to be a focus for the JTAMS PM.
Our Focus will be on Post-CDR, MS C and on planning for how we will transition JTAMS (1 and 2) to the field and support it!
This Practicum allows more freedom to develop solutions on your own. Team brainstorming is a good thing!
Practicum 4 Introduction 9

10. Practicum 4 Timeline
Practicum 4 Introduction 10 10

11. Marching Orders Lesson Plan Status
Systems Acquisition Activities Review
JTAMS Update
Marching Orders
Practicum 4 Introduction
March 2014

12. Practicum 4 Overview
During this Practicum, 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.
Section 1: Post-CDR Agile Measures Section
Section 2: Post-CDR JTAMS Measures Section
Section 3: SW Management Section
Section 4: Lean SW Development Section
Section 5: Cloud BCA Section
Practicum 4 Introduction

13. Practicum#4 Instructions
Practicum 4 consists of five sections designed to address real world post-CDR situations.
Each team will develop the practicum solution slide package using the templated slides provided, the given scenario, and the artifacts provided 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)
You will have 2 hours to read, research and brainstorm your solutions. You should use the provided slide templates as the basis for your presentation and add to them as appropriate to refine your briefing,
The instructors will designate which section each team will brief.
Practicum 4 Introduction 13

14. Team / Section Assignments (P4)1
1, 4 2
4, 2 3
3, 5 4
2, 4 5
5, 3
Practicum Sections
Section 1: Post-CDR Agile Measures Section
Section 2: Post-CDR JTAMS Measures Section
Section 3: SW Management Section
Section 4: Lean SW Development Section
Section 5: Cloud BCA Section
Teams will research and prepare to present based on the assignments above. Specific team/section presentation assignments will be announced by the instructors during the research period – remember all assigned sections will be graded for all teams.
Practicum 4 Introduction

15. Marching Orders
Go to your Student CD and open the folder for this Practicum.
Start by reviewing the student template slides and the artifacts/scenarios/instructions in the Job Aids folder.
Time
Event
Misc
2:30 – 4:45 (Day 9)
Practicum intro and research
Instructor and teams
4:45 (Day 9)
Submit Analysis
Submit electronically on BB or shared drive AND hard copy
Student Presentations
Instructors will designate which section(s) each team will brief
Instructor Wrap up
Instructor
The instructors will designate which section each team will brief before/during the practicum briefing period.
Practicum 3
March 2014 15