JTAMS POST-CDR IT/SIS ISSUES

Slides:



Advertisements
Similar presentations
TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.
Advertisements

TITLE OF PROJECT PROPOSAL NUMBER Principal Investigator PI’s Organization ESTCP Selection Meeting DATE.
What is Business Analysis Planning & Monitoring?
Requirements Specification for Lab3 COP4331 and EEL4884 OO Processes for Software Development © Dr. David A. Workman School of Computer Science University.
1 SPSRB Decision Brief on Declaring a Product Operational Instructions / Guidance This template will be used by NESDIS personnel to recommend to the SPSRB.
Texas Nodal Program ERCOT Readiness Update TPTF March 31, 2008.
Information Systems System Analysis 421 Class Three Initiating and Planning Systems Development Projects.
OIRM Business Process Planning Overview for Business & Operations Advisory Committee May 27 – 28, 2015.
Evaluate Phase Pertemuan Matakuliah: A0774/Information Technology Capital Budgeting Tahun: 2009.
JTAMS PRE-CDR IT/SIS ANALYSIS
JTAMS POST-CDR IT/SIS ISSUES
Principal Investigator ESTCP Selection Meeting
JTAMS POST-CDR IT/SIS ISSUES
Technical Business Consultancy Project
Civil Contractors Federation ‘2017 Earth Awards’ Submission Template CATEGORIES 1 and 2 ONLY Company Name (NOTE: if an Alliance then the name of the.
HRM 498 ASSIST Experience Tradition/hrm498assist.com
JTAMS PRE-CDR IT/SIS ANALYSIS
Lean Six Sigma DMAIC Improvement Story
ISA 201 Intermediate Information Systems Acquisition
Lesson 5 Materiel Solution Analysis (MSA) Exercise Team#
Principal Investigator ESTCP Selection Meeting
JTAMS MILESTONE A ANALYSIS
Coverage of exercise tasking and quality of solution (30 Points)
JTAMS POST-CDR IT/SIS ISSUES
JTAMS PRE-CDR IT/SIS ANALYSIS
ISA 201 Intermediate Information Systems Acquisition
AMRU Release 2 Release Report
JTAMS POST-CDR IT/SIS ISSUES
ISA 201 Intermediate Information Systems Acquisition
Product Support BCA Exercise – JRATS/JTAMS
ISA 201 Intermediate Information Systems Acquisition
JTAMS PRE-MILESTONE B ANALYSIS
FEASIBILITY STUDY Feasibility study is a means to check whether the proposed system is correct or not. The results of this study arte used to make decision.
JTAMS PRE-MILESTONE B ANALYSIS
Hyper-V Cloud Proof of Concept Kickoff Meeting <Customer Name>
Steering Committee Meeting
JTAMS PDSS Risk Assessment and Mitigation Plans
Phase 2 Tollgate Review Discussion Template
Phase 4 Tollgate Review Discussion Template
Phase 4 Tollgate Review Discussion Template
Lean Six Sigma DMAIC Improvement Story
Chapter 4 Systems Planning and Selection
Air Carrier Continuing Analysis and Surveillance System (CASS)
CMGT 445 Competitive Success/snaptutorial.com
BUS 519 Education for Service-- snaptutorial.com.
CMGT 445 Education for Service/snaptutorial.com
BUS 519 Teaching Effectively-- snaptutorial.com
CMGT 445 Teaching Effectively-- snaptutorial.com.
JTAMS PRE-CDR ANALYSIS
Lean Six Sigma DMAIC Improvement Story
Phase 4 Tollgate Review Discussion Template
Quarterly Business Review – SAMPLE DATA
Phase 2 Tollgate Review Discussion Template
Successful IT Projects By Darren Dalcher & Lindsey Brodie
IS&T Project Reviews September 9, 2004.
Project Management Process Groups
Phase 2 Tollgate Review Discussion Template
ATS Architecture Design Solution Intent
Employee engagement Delivery guide
Principal Investigator ESTCP Selection Meeting
Civil Contractors Federation ‘2014 Earth Awards’ Submission Template CATEGORIES 1 and 2 ONLY Company Name (NOTE: if an Alliance then the name of the.
Overview Headlines SIP Summary of progress High level plan
JTAMS Post-Milestone C Analysis
Principal Investigator ESTCP Selection Meeting
JTAMS PRE-MILESTONE B ANALYSIS
Answer the following questions:
JTAMS PRE-CDR ANALYSIS
JTAMS PRE-MILESTONE B ANALYSIS
CJA/475 FORECASTING AND STRATEGIC PLANNING The Latest Version // uopcourse.com
CJA/475 CJA/ 475 cja/475 cja/ 475 FORECASTING AND STRATEGIC PLANNING The Latest Version // uopstudy.com
Presentation transcript:

JTAMS POST-CDR IT/SIS ISSUES PM JTAMS

Scope of Presentation 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

Agile Measures Section Overview: It is approximately 3 months after CDR (May FY3). AMRU has continued STIM development and has produced measures and reports highlighting their progress as well as working software. Objective: Evaluate information and present an overview of the current status of STIM development (see Student Template) SEE: Practicum 4\Post-CDR Agile Measures Section 1

Present an overview of the schedule and identify any updates to the overall JRATS/JTAMS scenario Joint Training and Maintenance System (JTAMS) Increment 1 Government Roadmap Schedule Showing STIM (in green) SEE: Practicum 4\Post-CDR Agile Measures 4

Using the Cumulative Flow Diagram, explain what happened in April and May FY03. identify the work completed, work in progress and the work remaining on 03/01/03. Explanation In-Progress Work Remaining Work Complete Section 1 SEE: Practicum 4\Post-CDR Agile Measures

Explain the defect closure measurement Explain the defect closure measurement. Does it correlate with the other measurements? Why or why not? SEE: Practicum 4\Post-CDR Agile Measures

Measurement Section – JRATS/JTAMS Overview: It is approximately 6 months after CDR. Your team in the JTAMS program office has received a set of slides from Juggernaut depicting the current status of the overall JTAMS development. Objective: Evaluate information and provide recommended alternatives. Assess the updated measures delivered by Juggernaut Recommend alternatives for the PM See Section 2 JTAMS Measures Section 2

JTAMS MEASURES ASSESSMENT Summarize your analysis Worksheet #1 – Part 1 Problems Summarize any problems you identified, and identify root causes. Impacts Describe the source and scope of the problem and assess the potential impacts on project success. Outcome Predict the outcome if no action is taken, and indicate how this prediction was derived. See Section 2 JTAMS Measures

Justification Overview Display the key indicator slides that justify your analysis on the previous slide: See Section 2 JTAMS Measures

JTAMS MEASURES ASSESSMENT Provide alternatives given your analysis Worksheet #1 – Part 2 (Alternatives) Alternatives List the alternative courses of action you would consider for the program.   See Section 2 JTAMS Measures

Section 3 Software Management You will find data in the Job Aids relating to an emerging software management issue. The PM wants a summary of this issue and any insights your team has regarding the issue (see the Software Error Report included below and other artifacts in the Job Aids). Are there procedures to ensure that management information is transmitted throughout the software organization, and does the plan call for integrated information across all subcontracts as well as prime contractor developed software? Have plans been developed for resolution of actual and potential problems? See Section 3 Software management Section 3

Answer (Justify your answer): Are there procedures to ensure that management information is transmitted throughout the software organization, and does the plan call for integrated information across all subcontracts as well as prime contractor developed software? Answer (Justify your answer): Suggested resolution: See Section 3 Software management

Answer (Justify your answer): Have plans been developed for resolution of actual and potential problems? Answer (Justify your answer): Suggested resolution: See Section 3 Software management

Lean SW Development Section 4 The PM has indicated he would like an assessment of any aspect of the program that is using Agile software development. The PM understands that there are some Lean concepts that should be implemented as part of any Agile development and he wants to ensure that increment 2 of JTAMS fully leverages Lean concepts as part of any Agile development approach. For the lean-Agile assessment you will find an article the PEO provided. You will assess AMRU’s current Agile development approach and determine which aspects are in keeping with a lean approach. You will also recommend areas where AMRU might benefit from investigating additional Lean concepts. See Section 4 Lean SW Development Section 4

Agile / Lean assessment recommendations: Description Agile/Lean Assessment: The team recommends the following areas where AMRU and/or Juggernaut might benefit from investigating additional Lean concepts. Agile / Lean assessment recommendations: Lean Concept Description Addressed in AMRU overview Recommended for AMRU Sw Dev Plan (Describe expected benefit) Inventory in software development. Motion in software development. Waiting in software development. Over-production in software development. Over-processing in software development. Transport in software development. Defects in software development. See Section 4 Lean SW Development

Section Requirements: Cloud BCA Section The JTAMS PM is looking for a Cloud Service Provider (CSP) as an alternative hosting solution for its web-based applications because the Army has not designated the current Program Director Hosting Service (PD HS) at Fort Lincoln as an enduring data center. Section Requirements: Provide an overview (Executive Summary) of the overall scenario and the Section requirements to include the presentation overview. Identify and justify the IIL required for the program; Describe the impacts to the program Provide an overview of the program Cloud transition requirements Compare and contrast the capabilities of the two cloud service providers Identify 3 risks to the program (based on the requirements and capabilities provided) Provide an Section summary/conclusion/recommendation See Section 5 Cloud Section 5

Scenario and Presentation Overview See Section 5 Cloud

Information Impact Level Identify and justify the IIL required for the program: Describe the impacts to the program inherent in the required impact level: See Section 5 Cloud

Overall Rec. Primary Rationale Overview of Program Cloud Transition Requirements / Provider Capability Comparison Capability Overview of Capability/Terminology AWS* DISA MilCloud* Derived Requirements / Explanations / Discussion Cloud Capabilities Security Ease of Migration Management / Monitoring DR / COOP Governance Total (less Cost) Costs $110k $327k See Section 5 Cloud Overall Rec. Primary Rationale *1: No Capability; 2: /Low Capability; 3: Some Capability 4: Most Capability 5: Full Capability

Risk Analysis Identify 3 risks to the program (based on your selected provider). Present risk statements for your three risks and present your risks using a risk cube. Focus your risk analysis on the following categories: Security, Support, Staffing, and Governance. 1 2 3 4 5 See Section 5 Cloud P C S P C S P C S Yellow = Medium Risk Green = Low Risk Red = High Risk Risk Management

Cloud Section Summary/Conclusion Summarize the Requirement 2. Summarize the Cloud Provider Capability Comparison Results 3. Summarize the risks and impacts to the program: 4. Provide an overall Recommendation/Conclusion: See Section 5 Cloud