Enterprise_Project_Management_Process.pdf
PDF 1 MB Posted
- Attached to
- Information Technology Engineering Support Services (ITESS) Federal contract opportunity
- Solicitation number
- N32205-19-R-1000
About this file
This document contains a pre-solicitation notice for information technology engineering support services. The Military Sealift Command plans to release solicitation number N32205-19-R-1000 on or around November 19, 2018 to procure ITESS through a lowest price technically acceptable source selection method. Offers will be due on or around December 19, 2018. The procurement is set aside entirely for small businesses. The services sought include engineering support for IT systems, with an anticipated award amount and contract line items to be determined. The pre-solicitation provides potential offerors advance notice of the forthcoming solicitation for these ITESS requirements.
Enterprise Project Management Process
View the file
Other files for this federal contract opportunity
Show all 46
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Enterprise Project Management Process In te gr at ed
P ro je ct
T ea m
TC
IB
C us to m er
Initiation Phase
Test PhaseBuild PhaseDesign PhaseDefine Phase Project Closeout
Deploy Phase
CRQ is approved by Pre-Select Board; Completed N6 Project Planning Initiation Template provided by
Portfolio Manager
PDR SDR TRR DRR
PIR = Project Initiation Review PDR = Project Definition Review SDR = Solution Design Review TRR = Test Readiness Review DRR = Deployment Readiness Review DCR = Deployment Complete Review PCR = Project Closeout Review
Is Project Charter Approved
Rework Requested
No
Yes
Warranty Phase
No
Is Closeout Package AcceptedNo
Is BCA Selected and Approved
Rework Requested
DCR PCR
Rework Requested
Yes
Cancel Project and notify stakeholders
Cancel Project and notify stakeholders Cancel Project and notify stakeholders
Yes
Await TCIB Ranking and approval for execution;
Send to EPM Customer
(typically Service Delivery)
TCIB has approved the BCA; Ranked the project and approved for execution; Completed N6 Project Execution Initiation Template provided by Program
Manager
PIR
Initiate Phase Define Phase
In te gr at ed P ro je ct T ea m
C us to m er
Develop Project Charter and TCIB Project Slide;
Obtain IPT acceptance
Develop Draft Project
Schedule Milestones;
Develop Draft Cost estimate
(ROM) Assign Core Project
Planning Team (by name)
Assemble core Project
Planning Team (by role)
CRQ is approved by Pre-Select Board, Portfolio Manager has completed and provided “N6
Project Planning Initiation Template”.
Perform Operational
Needs Assessment
Identify and engage
Stakeholders;
Develop CPIC
Communication Plan; Identify
Organizational Process Assets
Yes
Identify project dependencies, constraints, Enterprise
Environmental Factors, and required project deliverables Conduct Project
Initiation Review
Attend Project Initiation Review
Is PIR Successful
No Rework Phase Deliverables as needed;
If the PIR is NOT approved, the IPT & Program Manager may cancel the project or rework the phase deliverables.
Continue to Define Phase
Define Phase
Design Phase
C us to m er In te gr at ed
P ro je ct
T ea m
Perform Technical comparison of alternatives
Is PDR Successful
Develop Requirements
Traceability Matrix
Gather and Document High-
Level System Requirements;
Conduct Prelim- Req’mnts Review
No
Develop Draft Risk Management Plan
& Risk Register
Identify IA/C&A Needs; Assemble
DIACAP team;
Determine
Accreditation Requirements
Identify EA/TA Needs and develop EA/TA Plan as needed
Attend PDR
Perform Needs Analysis, 5 W’s, Gather Operational
Requirements and Develop ORD
Prepare for and Conduct Project
Definition Review
(PDR)
Develop high-level WBS for each alternative
Establish Technical
Evaluation Criteria for AoA
Develop BCA Package (including
AoA, Risk Plan, Comms Plan, Funding Profile and POA&M
Yes
Develop Cost and Schedule estimates for each alternative
Rework Phase Deliverables as needed;
If the PDR is NOT approved, the IPT & Program Manager may cancel the project or rework the phase deliverables.
From Initiate Phase; No
Is Project Charter approved
Cancel Project and Notify Stakeholders
Submit Project Charter to
TCIB
Await TCIB decision;
Dissolve IPT
Champion BCA package at TCIB
Yes
Define Initial Testing
Requirements
Develop Schedule, Cost, and RLN to
AoA; Plan IPT Communications.
Yes
Identify existing assets (Hardware, Software, Systems, etc.) that may satisfy requirements
The BCA submission may require supporting documentation, including the Preliminary System Requirements Specification and a CPIC Project Slide; For large efforts, a Command Council Brief may be required.
C us to m er
TC
IB
From Define Phase;
Cancel Project and Notify Stakeholders
Is BCA Package approved & is the solution selected?
Hold in Service Pipeline (TCIB
Ranking);
At this point, the project will be restarted according to N6 prioritization and funding
Submit BCA Package to TCIB
Review BCA Package
TCIB Ranking
No
Rank and Prioritize
Complete N6 Project Execution
Initiation Template
Yes
Continue to Design Phase
This process is outside the scope of EPM but is included here for reference.
Design Phase
Build Phase
In te gr at ed P ro je ct T ea m
C us to m er
Develop Initial C&A Package
Update Project Plan & RLN, Develop Schedule & Cost through
Design Phase for Selected Solution
Is SDR Successful
Develop detailed System
(Technical) Requirements
Specification and Requirements
Traceability Matrix
Conduct Solution Design Review
(SDR);
Baseline cost & schedule (RLN)
Develop TEMP;
Include Design
Verification, Integration and UAT test cases
Finalize Solution Design
Specification and Requirements
Traceability Matrix
Yes
Attend SDR
Attend Project Kickoff
Conduct Kick Off & confirm resource availability
Identify New Integrated Project Team & Develop
Project Communications
Plan
Develop Solution Design
Specification including System
Devices
Develop Draft Standard Operating
Procedures
Update EA/TA
Prepare baseline Project WBS, Schedule and Cost
(POA&M/RLN)
through Test Phase (ROM
Deploy phase)
No
Rework Phase Deliverables as needed;
If the SDR is NOT approved, the IPT & Program Manager may cancel the project or rework the phase deliverables.
Continue to Build Phase
From TCIB Ranking;
Have TCIB BCA approval, selected solution;
Program Manager supplies a completed N6 Project Execution Initiation Template.
Conduct IA Kickoff and initiate package
Draft TRANSALT Forms and/or Operations
Checklist (as required)
Build Phase
Test Phase
In te gr at ed P ro je ct T ea m
C us to m er
No
Submit C&A Package for IATT to ODAA
Complete Procurement and
Prepare Development
Environment for Build
Is C&A Package approved
Build Application and Infrastructure as per the Design
Specification;
Perform and
Document Unit Testing
Finalize TEMP (Test and
Evaluation Master Plan)
Update C&A Package and prepare for submission
Perform System Maintenance to remediate IA Vulnerabilities
Is TRR Successful
Prepare for and Conduct Test
Readiness Review
(TRR)
Yes
Perform System Maintenance to remediate IA Vulnerabilities
Attend TRR
Develop Deployment &
Rollback Plan and Standard Operating
Procedures (SOPs)
Receive signed IATT Letter (approval to connect testing environment)
Yes
Perform System Maintenance to remediate IA Vulnerabilities
No
Review Project artifacts and solution design with Operations and confirm environmental assumptions
Complete and submit updated
TRANSALT
documentation (as required)
Update Operations Checklist
From Design Phase
Rework Phase Deliverables as needed;
If the TRR is NOT approved, the IPT & Program Manager may cancel the project or rework the phase deliverables.
Continue to Test Phase
Test Environment Checklist
Draft Global Service Desk
(GSD) Checklist
Test Phase
Deploy Phase
In te gr at ed P ro je ct T ea m
C us to m er
Yes
No
Scan & Update C&A Package
Manage Defects
Submit C&A Package for ATO to ODAA
Perform Design Verification Testing & document results
Is C&A Package approved
Perform Integration Testing
& document results
Perform User Acceptance
Testing (UAT) & document results
Receive ATO Letter
Deliver project artifacts to
Configuration Management and
Conduct Deployment
Readiness Review
(DRR)
Is DRR Successful
Perform System Maintenance to remediate IA Vulnerabilities
Provide Input to Develop
Deployment Schedule
Yes
Test and Finalize Deployment &
Rollback Plan and SOPs (Test Installation)
Develop (with Execution Manager)
Deployment Schedule
(POA&M)
Yes
Attend DRR
All critical defects resolved?
No
Perform System Maintenance to remediate IA Vulnerabilities
Perform System Maintenance to remediate IA Vulnerabilities
Create Training Documents
Test Installation Successful
No
NoFinalize Global Service Desk
Checklist
Finalize Operations Checklist
Update EA/TA artifacts
Yes
From Build Phase
If defects are not resolved, IPT and Customer determine best course of action to correct defects and repeat testing;
Under extreme failure conditions, the IPT may recommend the Program
Manager cancel the project
Rework Phase Deliverables as needed;
If the DRR is NOT approved, the IPT & Program Manager may cancel the project or rework the phase deliverables.
Continue to Deploy Phase
If a TRANSALT is required, approval is required prior to Testing and Finalizing Deployment & Rollback Plan.
Deployment Availability information is needed from Execution Manager and Afloat Operations
Deploy Phase
Project Close Out Phase
In te gr at ed P ro je ct T ea m
In cl ud in g E xe cu tio n
M an ag er an d E xe cu tio n
B ra nc h
C us to m er
Roll Back the Solution
Conduct Deployment Complete
Review (DCR)
Is Solution Accepted?
Deploy Solution as per
Deployment Plan
Complete Pilot or Mock Install
Validate Solution
Deployment yes
No
Test and Finalize Training
Document
Finalize Deployment
Schedule
(POA&M)
YesIs DCR Successful
Attend DCR
No
During the Deployment Phase, the Execution Manager leads most daily activities. The Project Manager and IPT are available primarily to support the Program Manager and ensure a successful solution handoff to the Execution Manager.
Many solutions require multiple installations, this is especially true for Afloat systems. The deploy, validate, accept/rollback cycle may be repeated.
If a rollback is required, the approved rollback plan will be followed. The program manager, execution manager, and project manager will then assemble an appropriate team to assess the situation and develop an action plan.
From Test Phase
Provide Training (as required)
Rework Phase Deliverables as needed;
If the DCR is NOT approved, the IPT & Program Manager may cancel the project or rework the phase deliverables.
Continue to Project Closeout Phase
Project Close Out Phase
Warranty Phase
In te gr at ed P ro je ct T ea m
C us to m er
Deliver HW/SW to Operations (as required)
Identify and Agree on Warranty support period.
Define and document any Warranty SLA’s and support agreements
Identify & Document Final
Lessons Learned
No
No
Update Appropriate
Organizational Process Assets (Particularly EA/
TA artifacts)
Prepare Project
Closeout Package for
TCIB
Review Project Close out
Package and Submit it to
TCIB
Is Package Accepted?
Plan Warranty Activities
Send request to Change
Management requesting CRQ
Closure
Yes
From Deploy Phase
Rework Phase Deliverables as needed;
However unlikely, the TCIB could cancel the project at this point.
Conduct Project
Closeout Review
Attend Project
Closeout Review
Is PCR Successful
Continue to Warranty Phase;
Dissolve the IPT retaining only enough support for Warranty; close project
Rework Phase Deliverables as needed;
If the PCR is NOT approved, the IPT & Program Manager may cancel the project or rework the phase deliverables.
Submit Project Artifacts to CM and archive on
IS Portal; ensure SOPs delivered to applicable parties
Create Project Closeout Review
Brief
Warranty Phase
In te gr at ed
P ro je ct
Te am C us to m er
Conduct Warranty Activities;
Provide Support During the Defined
Warranty Period
End
From Project Closeout Phase
Finalize Warranty Activities
Review Warranty Activities and
Report Status (as required)
Warranty Phase Activities and Reporting are governed by the approved Warranty Agreement and the Technical Support Services Process.
Assign Dedicated Warranty Point of
Contact
| EPM Binder Intro Pages |
| Military Sealift Command (MSC) Enterprise Project Management (EPM) Handbook Version 1.0 Published November 2011 Process Owner: Rick Martin |
| EPM Executive Summary |
| Location of Latest Templates |
| Feedback |
| EPM Handbook Table of Contents |
| SECTION A - EPM PROCESS DOCUMENTS |
| SECTION B - OVERARCHING FRAMEWORK DOCUMENTS |
| SECTION C – EPM ARTIFACT TEMPLATES |
| PLANNING |
| INITIATE PHASE |
| DEFINE PHASE |
| EXECUTION |
| DESIGN PHASE |
| BUILD PHASE |
| TEST PHASE |
| DEPLOY PHASE |
| CLOSEOUT PHASE |
| WARRANTY |
| WARRANTY PHASE |
| SUPPORTING DOCUMENTATION |
| Template_Tracker |
| Artifact Template List |
| Enterprise_ProjectManagemet_ProcessFlow |
| Overview� |
| Initiate Phase� |
| Define Phase� |
| TCIB Ranking� |
| Design Phase� |
| Build Phase� |
| Test Phase� |
| Deploy Phase� |
| Project Closeout� |
| Warranty Phase� |
| Enterprise_Project_Management_Methodology |
| Project Milestones� |
| Enterprise_Project_Management_Methodology_Deliverables |
| Project Milestones� |
| MSC_N6_OverarchingFrameworkRACIMatrix |
| 3 RACI Chart |
| Table 1 - N6 RACI Chart for Deliverying Normal Changes |
| MSC_N6_OverarchingFrameworkProjectManagementDiscipline |
| Project Management |
| 4.4.1 Purpose |
| 4.4.2 Relation to Other Disciplines |
| Authority |
| Process and Guidance |
| Table 1 – Project Management Process and Guidance Documents |
| Table 2 – Project Management Process and Guidance Templates |
| Reporting Requirements |
| Table 3 – Project Management Reporting Requirements |
| Inputs to and Outputs from Project Management |
| Table 4 – Project Management Inputs and Outputs |
| 01-CPIC-TEMPLATE-ProjectCharter |
| 2.1 Project Background |
| 2.2 Needs |
| 2.3 Justification for Change |
| 2.4 Objectives |
| 2.5 IT Strategic Goal Alignment |
| 3 PROPOSED ALTERNATIVES |
| 4.1 Integrated Project Team |
| 4.2 Project Team |
| 5.1 Project Life Cycle |
| 5.2 Measures of Effectiveness and Performance |
| 5.3 Assumptions |
| 5.4 Constraints |
| 5.5 Dependencies |
| 6 Lessons Learned |
| 7 Project Documentation |
| 8.1 ROM Cost Estimates |
| 8.2 Major Milestone Schedule Estimates |
| 9.1 Change History |
| 9.2 Integrated Project Team Approval signatures are in Section 4.1 |
| 9.3 Deputy, Plans, N6XP Approval |
| 9.4 Final Approval |
| 01-CPIC-Template-ProjectCharterSlides |
| Slide Number 1 |
| 01-CPIC-TEMPLATE-CommunicationsPlan |
| Version History |
| 1 Project Information |
| 2 Project Stakeholders |
| 3 Project Team Members: |
| 4 Required Communications |
| Template_PIRChecklist |
| 02-CPIC-TEMPLATE-AoA |
| 1 DESCRIPTION OF ALTERNATIVES |
| 2 ALTERNATIVE SELECTED |
| 2.1 Justification for Selection |
| 2.2 IT Strategic Goal Alignment |
| 2.2.1 Advantages and Key Requirements |
| 2.2.2 Additional Justification |
| 3 ALTERNATIVES CONSIDERED AND REJECTED |
| 4 ALTERNATIVE IDENTIFICATION AND SELECTION PROCESS |
| 4.1 Market Research |
| 4.2 Applied Lessons Learned |
| 03-CPIC-TEMPLATE-RiskPlan |
| Details |
| Summary |
| Template Guidance |
| 04-CPIC-TEMPLATE-FundingProfile |
| SAMPLE |
| Status Quo |
| Alternative 2 |
| Alternative 3 |
| Alternative 2 vs. Status Quo |
| Alternative 3 vs. Status Quo |
| Summary |
| Summary 2 |
| 05-CPIC-Template-BCASlides |
| Slide Number 1 |
| Slide Number 2 |
| TEMPLATE_MSCCBriefingSlides |
| MSCC Briefing |
| Agenda |
| Slide Number 3 |
| Improving Afloat IA �Agenda |
| Purpose |
| Background |
| Issues |
| Courses of Action |
| Recommendation |
| TEMPLATE_ORD |
| 1 INTRODUCTION |
| 1.1 Purpose of the ORD |
| 1.2 Project Identification |
| 1.3 Scope |
| 1.4 Assumptions |
| 1.5 Constraints |
| 2 GENERAL DESCRIPTION OF THE TARGET OPERATIONAL CAPABILITY |
| 2.1 Capability Gap |
| 2.2 Overall Business Area and Mission Description |
| 2.3 Description of the Proposed System |
| 2.4 Supporting Analysis |
| 2.5 Operational and Support Concept |
| 2.5.1 Concept of Operations |
| 2.5.2 Support Concept |
| 3 EXISTING SYSTEM |
| 3.1 General Description of the Current System |
| 3.2 Existing System Deficiencies |
| 4 CAPABILITIES REQUIRED |
| 4.1 Operational Capabilities |
| 4.2 Key Performance Parameters |
| 4.3 System Performance |
| 4.3.1 Use Cases |
| 4.3.2 System Performance Parameter |
| 4.3.3 Interoperability |
| 4.3.4 Human Interface Requirements |
| 4.3.5 Logistics and Readiness |
| 4.3.6 Other System Characteristics |
| 5 SYSTEM SUPPORT |
| 5.1 Maintenance |
| 5.2 Supply |
| 5.3 Support Equipment |
| 5.4 Training |
| 5.5 Transportation and Facilities |
| 6 FORCE STRUCTURE |
| 7 SCHEDULE |
| 8 SYSTEM AFFORDABILITY |
| 9 ACRONYMS |
| TEMPLATE_SysReqSpec |
| 1 INTRODUCTION |
| 1.1 Purpose |
| 1.2 Scope |
| 1.3 Proposed System Overview |
| 1.4 Objectives |
| 1.5 Assumptions |
| 2 CONSTRAINTS |
| 2.1 System Constraints |
| 2.2 Legal or Regulatory Constraints or Limitations |
| 3 SYSTEM REQUIREMENTS |
| 3.1 Functional Requirements |
| 3.1.1 Reporting Requirements |
| 3.2 Performance Requirements |
| 3.3 Behavioral Requirements |
| 3.4 Interface Requirements |
| 3.4.1 Internal Interface Requirements |
| 3.4.2 External Interface Requirements |
| 3.4.3 Human Interface Requirements |
| 3.5 Quality Requirements |
| 3.5.1 Reliability Requirements |
| 3.5.2 Usability Requirements |
| 3.5.3 Maintainability Requirements |
| 3.5.4 Portability Requirements |
| 3.5.5 Availability Requirements |
| 3.5.6 Applicable Standards |
| 3.5.7 Scalability Requirements |
| 3.5.8 Interoperability Requirements |
| 4 SUPPLEMENTAL REQUIREMENTS |
| 4.1 Service Level Agreements |
| 4.2 Data Requirements |
| 4.3 Security Requirements |
| 4.4 Environmental Requirements |
| 4.5 System Administration Requirements |
| 4.6 Logistics and Support Requirements |
| 4.7 Computing Requirements |
| 4.8 Installation and Adaptation Requirements |
| 4.9 Documentation Requirements |
| 4.10 Other Requirements |
5 ACRONYMS
| TEMPLATE_RTM |
| Instructions |
| Cover Sheet |
| Change Record |
| RTM |
| TEMPLATE_RiskMgmtPlan_Register |
| Instructions |
| Cover Sheet |
| Change Record |
| Risk Management Plan |
| Risk Register |
| Pre-Populated Risks |
| TEMPLATE_PDRChecklist |
| 08-CPIC-Template-RebaselineSlides |
| Slide Number 1 |
| 06-CPIC-TEMPLATE-FundingProfileRebaseline |
| Approved |
| Rebaseline |
| Cost Delta (calculated) |
| TEMPLATE_ProjectCommunicationsPlan |
| 1 PROJECT INFORMATION |
| 2 PROJECT STAKEHOLDERS |
| 3 PROJECT TEAM MEMBERS: |
| 4 REQUIRED COMMUNICATIONS |
| 5 ACRONYMS |
| TEMPLATE_SolutionDesignSpec |
| 1 PROJECT PURPOSE |
| 1.1 Project Description |
| 1.2 Document Overview |
| 2 SCOPE |
| 2.1 Identification |
| 2.2 System/Solution Overview |
| 3 SYSTEM DESIGN |
| 3.1 Design Assumptions and Constraints |
| 3.2 External Agreements |
| 3.3 Design Considerations and Decisions |
| 3.4 Security Considerations |
| 3.5 System Inputs and Outputs |
| 3.6 System Behavior |
| 3.7 System Data |
| 4 SOLUTION DESIGN SPECIFICATION ENVIRONMENT/SOLUTION |
| 4.1 Environment/Solution Architecture |
| 4.1.1 System Name |
| 4.1.2 Classification |
| 4.1.3 Environmental Description |
| 4.1.4 System Breakdown Structure (SBS) |
| 4.1.5 System Interface Description SV-1 |
| 4.1.6 Systems Communications Description SV-2 |
| 4.1.7 Other Diagrams |
| 4.1.8 Accreditation Boundary Diagram |
| 4.1.9 Network Identification |
| 4.1.10 SNMP |
| 4.1.11 Firewall |
| 4.1.12 SMTP |
| 4.2 Device Information |
| 4.3 Interface Design |
| 4.3.1 Inter-System Interfaces |
| 4.3.2 Intra-System (Internal to Internal) Interfaces |
| 4.4 Users |
| 4.4.1 Access Specifications |
| 4.4.1.1 Normal |
| 4.4.1.2 Administrative |
| 4.4.1.3 Remote Administrative |
| 4.4.1.4 Elevated (Non-administrative) |
| 4.4.1.5 Maintenance |
| 4.4.1.6 Restricted |
| 4.4.1.7 Other |
| 4.5 Data |
| 4.5.1 Data Storage Specifics |
| 4.5.2 Data Retention and Recovery |
| 4.5.3 Data Availability |
| 4.5.4 Clustering, Replication, Mirroring, Load Balancing |
| 4.5.5 Data Encryption Specifics |
| 4.6 Software |
| 4.6.1 Operating System Software |
| 4.6.2 Application Software |
| 4.6.3 Administrative Software |
| 4.7 Performance Estimates |
| 4.8 Disaster Recovery |
| 5 REQUIREMENTS ALLOCATION |
| 6 FUTURE CONSIDERATIONS |
| 7 ACRONYMS |
| TEMPLATE_SolutionDesignSpecSystemDevices |
| Cover Sheet |
| Change Record |
| System Devices |
| TEMPLATE_SOP |
| 1 PURPOSE |
| 2 SCOPE |
| 3 PREREQUISITES |
| 4 ROLES AND RESPONSIBILITIES |
| 5 PROCEDURES |
| 5.1 Subsection |
| 6 TRAINING |
| 7 MONITORING REQUIREMENTS |
| 8 REFERENCES |
| 9 ACRONYMS |
| TEMPLATE_TestEvaluationMasterPlan |
| 1 INTRODUCTION |
| 1.1 Purpose |
| 2 SCOPE |
| 3 LIMITATIONS AND TRACEABILITY |
| 3.1 Purpose |
| 3.2 Traceability (Functional Requirements Traceability Matrix) |
| 4 TEST PLAN |
| 4.1 Test Levels |
| 4.2 Subsystem Integration Testing |
| 4.3 System Test |
| 4.4 Verification Test |
| 4.5 Security Test |
| 4.6 SOP Test |
| 5 TEST ENVIRONMENT AND SCHEDULES |
| 5.1 System Description |
| 5.2 Milestones |
| 5.3 Organizations and Locations |
| 5.4 Schedule |
| 5.5 Resource Requirements |
| 5.6 Equipment |
| 5.7 Systems |
| 5.8 Personnel |
| 5.9 Testing Material |
| 5.10 Test Training |
| 5.11 Test Methods and Evaluation |
| 5.12 Methodology |
| 5.13 Conditions |
| 5.14 Test Progression |
| 5.15 Data Recording |
| 5.16 Constraints |
| 5.17 Criteria |
| 5.18 Data Reduction |
| 6 TEST DESCRIPTIONS |
| 6.1 Test Name |
| 6.2 Test Description |
| 6.3 Control |
| 6.4 Inputs |
| 6.5 Outputs |
| 6.6 Procedures |
| 6.7 Defect Reporting |
7 ACRONYMS
| TEMPLATE_OperationsChecklist |
| Ops Readiness items |
| TEMPLATE_SDRChecklist |
| TEMPLATE_DeployRollbackPlan |
| 1 INTRODUCTION |
| 2 PROJECT |
| 2.1 Project Overview |
| 2.2 Supporting Project Documentation |
| 3 DEPLOYMENT PLAN |
| 3.1 Type of Deployment |
| 3.2 Site Preparation of Notification |
| 3.3 Outage Required |
| 3.4 Notification Plan |
| 3.5 Data Protection Plan |
| 3.6 Timeline |
| 3.7 High-level Work Breakdown Structure |
| 3.8 Deployment Verification |
| 3.9 Deployment Resources and Roles |
| 4 ROLLBACK PLAN |
| 4.1 Rollback Type |
| 4.2 Rollback Criteria |
| 4.3 Notification Plan |
| 4.4 Data Restoration Plan |
| 4.5 Rollback Preparations |
| 4.6 Rollback Timeline |
| 4.7 High-level Work Breakdown Structure |
| 4.8 Rollback Verification |
| 4.9 Rollback Resources and Roles |
5 ACRONYMS
| TEMPLATE_UnitTestReport |
| 1 PURPOSE |
| 2 TEST SUMMARY OF MODULE |
| 3 DOCUMENTS REFERENCE |
| 4 TEST ASSESSMENT |
| 5 TEST RESULTS |
| 6 TEST DISCREPANCIES |
| 6.1 Resolved Test Discrepancies |
| 6.2 Unresolved Test Discrepancies |
| 7 ARCHIVE PLAN |
| 8 RECOMMENDATIONS |
| 9 ACRONYMS |
| TEMPLATE_TestEnvironAccessChecklist |
| TEMPLATE_GSDChecklist |
| TEMPLATE_TRRChecklist |
| TEMPLATE_TrainPlan |
| 1 PROJECT INFORMATION |
| 1.1 Introduction |
| 2 SCOPE |
| 3 OBJECTIVES |
| 4 BACKGROUND |
| 5 TRAINING REQUIREMENTS |
| 6 ROLES AND RESPONSIBILITIES |
| 7 TRAINING EVALUATION |
| 8 TRAINING STRATEGY |
| 9 TRAINING SOURCES |
| 10 DEPENDENCIES/CONSTRAINTS/LIMITATIONS |
| 11 TRAINING RESOURCES |
| 12 TRAINING ENVIRONMENT |
| 13 TRAINING MATERIALS |
| 14 UPDATE/REVISE TRAINING MATERIALS |
| 15 ACRONYMS |
| TEMPLATE_TrainSessionTeachPlan |
| 1 PROJECT INFORMATION |
| 1.1 Introduction |
| 2 TEACHING OBJECTIVES |
| 3 TEACHING PLAN |
| 4 ACRONYMS |
| TEMPLATE_TrainConfirmLetter |
| TEMPLATE_DRRChecklist |
| TEMPLATE_DCRChecklist |
| 12-CPIC-Template-LessonsLearnedStatusUpdate |
| Slide Number 1 |
| 07-CPIC-TEMPLATE-LessonsLearned |
| Lessons Learned |
| TEMPLATE_WarrantySupportAgreement |
| 1 PURPOSE |
| 2 JUSTIFICATION |
| 3 SCOPE |
| 4 ASSUMPTIONS |
| 5 RESOURCE PLAN |
| 6 SPECIFICS OF REQUEST |
| 7 STAKEHOLDER INFORMATION |
| 8 REQUIRED COMMUNICATIONS |
| 9 RESOURCE PLAN COST BREAKDOWN |
| 10 END RESULT |
| 11 ACRONYMS |
| TEMPLATE_PCRBrief |
| <Project Name> |
| Agenda |
| Overview and Scope |
| Scope Changes |
| Schedule – Project Milestones |
| Requirements |
| Technical – Diagrams �<if SV-2s are not available, describe the as-is and� to-be environments and the major differences or changes> |
| Engineering Artifacts�Define Phase |
| Engineering Artifacts�Design Phase |
| Engineering Artifacts�Build Phase |
| Engineering Artifacts�Test Phase |
| Engineering Artifacts�Deploy Phase |
| Engineering Artifacts�Closeout Phase |
| Technical – Phase Accomplishments |
| Project Costs� <costs will be included in the CR only> |
| Lessons Learned |
| Follow-on Projects |
| Project Closeout Review Checklist�<checklist will be included in the CR only> |
| TEMPLATE_PCRChecklist |
| TEMPLATE_WarrantySupportStatusReport |
| 1 PURPOSE |
| 2 COMPLETED ACTIVITIES |
| 3 CURRENT ACTIVITIES |
| 4 PLANNED ACTIVITIES |
| 5 SUPPORTING INFORMATION |
| 6 POTENTIAL IMPACTS ON SCHEDULE |
| 7 DOCUMENT LOCATION |
| 8 ACRONYMS |
| TEMPLATE_MeetingAgendaMinutes |
| TEMPLATE_ProjectPerformanceReport |
| 1 PURPOSE |
| 2 IPT MEMBERS |
| 3 PROJECT SCOPE |
| 4 PROJECT OBJECTIVE |
| 5 STATUS REPORT |
| 6 PROJECT PERFORMANCE ANALYSIS |
| 7 RISK |
| 8 ISSUES |
| 9 RECOMMENDATIONS |
| 10 ADDITIONAL COMMENTS |
| 11 SCHEDULE |
| 12 ACRONYMS |
| TEMPLATE_DecisionLog |
| Instructions |
| Cover Sheet |
| Change Record |
| Decision Log |
| TEMPLATE_ImpactAnalysis |
| 1 INTRODUCTION |
| 1.1 Executive Summary |
| 1.2 Purpose of Impact Analysis |
| 2 PROJECT DESCRIPTION |
| 2.1 Current Project Status |
| 3 REQUESTED CHANGE(S) |
| 3.1 Change # 1: <Title> |
| 3.1.1 Justification |
| 3.1.2 Source |
| 3.1.3 Type of Change |
| 3.1.4 Impact of Change #1 |
| 3.1.4.1 Technical Impact |
| 3.1.4.2 Impact by Phase |
| 3.1.4.2.1 Initiation Phase Artifacts and Activities |
| 3.1.4.2.2 Define Phase Artifacts and Activities |
| 3.1.4.2.3 Design Phase Artifacts and Activities |
| 3.1.4.2.4 Build Implementation Artifacts and Activities |
| 3.1.4.2.5 Test Implementation Artifacts and Activities |
| 3.1.4.2.6 Deploy Implementation Artifacts and Activities |
| 3.1.4.2.7 Closeout Implementation Artifacts and Activities |
| 3.1.4.3 Impact on Cost |
| 3.1.4.4 Impact on Schedule |
| 3.1.4.5 Impact on Technical Performance |
3.2 Change # 2: < Title>
| 4 FINDINGS |
| 5 ACRONYMS |
| TEMPLATE_ProgramLevelStatusReport |
| <Project Name> |
| Slide Number 2 |
| 11-CPIC-Template-ProjectStatusUpdateSlide |
| Slide Number 1 |
| TEMPLATE_ProjectPlanningInitiation |
| TEMPLATE_ProjectExecutionKickoff |
File details come from the government source that posted it. Updated .