Record of Changes # Date Reference A=Add M=Modify D=Delete Description of Change CR # 1 August 25, 2011 All A Initial Working Draft NA 2 January 27, 2012 Complexity Focus Group M Section 2, Project Complexity Description NA 3 March 05, 2012 Governance Team Review A, M Section 1 edits for clarity, added Section 1.4 on starting a project Section 2 and Section 6, removed references to Cost Estimation Tool (CET) Section 5 alignment and consistency changes, consolidated artifacts definition, removed references to core and recommended artifacts. Revised graphics for Figures 1-3, updated Figure 9 for consistency Revised Section 6, Appendix, to align with Section 5 updates NA 4 March 13, 2012 Governance Team Review M Updated Figures 3, 6-13 Updated Security Artifacts life cycle in Figure 9 and Sections 5 & 6 NA 5 March 14, 2012 CMS M Changed Table/Figure captions and references to them. Added List of Tables in TOC. NA 6 March 21, 2012 Governance Team Review A, M Modified Figure 3 for CL 2 Modified Section 6.2 to with CL 2 Figure 5 marked as sample. Sections 1.3 and 2 minor updates Section 4: added 4 roles, modified GO definition, deleted reference to ERR Section 5 minor edits NA 7 March 28, 2012 Governance Team Review M Modified Figure 3 to correct IAT definition to Independent Assessment Team Replaced Figure 5 with new Starting a Project graphic and revised accompanying text. N/A 8 April 5, 2012 CMS M Promoted Detailed Design Review to governance review for Complexity Level 3 Removal of Project Startup Review 2012-01 2012-02 9 April 16, 2012 Governance Team Review M Revised Figure 2: Expedited Life Cycle Process Flow, for improved 508 compliance, inclusion of the initial idea presentation NA 10 May 3, 2012 Governance Team Review M Revised Guidance Officer definition in Section 4 NA
11 May 16, 2012 Governance Team Review M Revised Section 4, XLC Roles, to include Investment Owner N/A 12 May 30, 2012 A Editing and 508 compliance N/A 13 August 10, 2012 CMS M Removed incorrect references to federally systems in Section 5. N/A 14 November 13, 2012 CMS M Removed most references to Guidance Officer in anticipation of new OIS Business/Technology Liaison role N/A 15 July 22, 2013 CMS M Security changes to Table 4 and related sections. 12-007 16 December 20, 2013 CMS M Changed XLC graphic Updated Table 1 (Complexity) Updated Table 4 (Artifacts) 13-002 13-008 12-007 17 August 27, 2014 CMS M references to Acquisition Strategy, per CR 14-002. Corrected the following errors: Removed the artifact “Disposition Closeout Certificate” from Table 4 and Section 5.5.3 on p. 38. This is not a valid artifact. Corrected definition of “CIRT” (p. 7) Removed all references to Guidance Officer (GO) Added System Retirement Memo to Section 5.5.3. 14-002 18 November 13, 2014 CMS M Performance Test Plan and Results Template. Updated the definition of the Post Implementation Review (PIR). 14-006 19 November 21, 2014 CMS M Added to System Security Plan to Table 4. This item was overlooked in a prior release. N/A 20 February 02, 2015 CMS M Updated CMS logo. N/A of Contents 1. CMS Expedited Life Cycle Introduction 1 1.1 High-Level Process Overview 1 1.2 Expedited Life Model 2 1.3 Project Process Agreement (PPA) 5 1.4 Starting an XLC Project 7 2. System Development XLC Options 8 2.1 Project Complexity Categories 8
Table 4 (continued): CMS XLC Artifacts by Phase PHASES Initiation Concept Planning Requirements Analysis Design Development Testing Implementation Operations & Maintenance Disposition ARTIFACTS/ INFORMATION REVIEWS AR ISR PBR RR ERR1 (VRR) ERR2 ERR3 (IRR, PRR) ORR PIR AOA DR System Design Document P/B Database Design Document P F Physical Database/Model P/F Interface Control Document P/B Data Use Agreement P I I F Test Case Specification P F Data Conversion Plan P F Computer Match Agreement/ Interagency Agreement P/F Implementation Plan P I I F User Manual P I I F Operations & Maintenance Manual P I I F Performance Test Plan and Results Template P I F Business Product/Code P/B Version Description Document P B Training Plan P/F Test Summary Report P F Training Artifacts P F System Disposition Plan P/F Post-Implementation Report P/F Annual Operational Analysis Report P/F Artifacts are completed per the Project Process Agreement Project Management Artifacts B – Baseline F – Final I – Interim P – Preliminary U – Update Yearly Security Artifacts Security Information from Tasks Systems Development Artifacts Reviews are conducted per the Project Process Agreement AR – Architecture Review ISR – Investment Selection Review PBR – Project Baseline Review RR – Requirements Review PDR – Preliminary Design Review DDR – Detailed Design Review ERR – Environment (Validation, Implementation, Production) Readiness Review ORR – Operational Readiness Review PIR – Post Implementation Review AOA – Annual Operational Analysis DR – Disposition Review
Low Schedule is less than 5% less than estimate on completed similar effort Cost High Estimate At Complete (EAC) exceeds budget by more than 10% Medium EAC exceeds budget between 5% and 10% Low EAC is less than 5% over budget Technical contractor experience High No experience delivering IT projects for CMS or another HHS department or agency Current Capability Maturity Model Integration assessment is less than 3 Medium At least one IT project with CMS or another HHS department or agency Current Capability Maturity Model Integration assessment equals 3 Low At least three successful IT projects with CMS Current Capability Maturity Model Integration assessment greater than 3 Overall Risk/ Opportunity High More than five risks identified and in mitigation Medium Between one and five major risks identified and in mitigation Low No major risks identified or all are currently mitigated XLC Phase – Requirements Analysis and Design Overview: During the Requirements Analysis and Design Phase, a common set of business rules are refined and the business requirements are validated and decomposed into functional and non-functional requirements. The requirements are used to define the design in detail, including inputs, processes, outputs, and interfaces as well as to permit further detailed project management planning. Detailed specifications are developed to support the IT solution that fulfills the requirements for a particular release. The requirements and logical description of the entities, relationships, and attributes of the data are defined and allocated into system and data design specifications. Initial traceability is started between requirements, design, and solution testing. These design specifications are organized specifically to be suitable for implementation and testing within the constraints of a physical environment (e.g., computer, database, and infrastructure). Perform the risk management tasks described in the RMH Volume I Chapter 1 Risk Management in the XLC at . The risk management tasks performed during this phase are: