waived in Release 1.1. Figures 9 (on page 22) and 10 (on page 23) demonstrate how, through the use of the PPA, reviews such as the AR and ISR will only occur during Release 1.0 of the project, subject to approval by the TRB. Figure : PRRS PPA Release 1.0 – Figure : PRRS PPA Release 1.1 – The PRRS IPT drafts and submits preliminary artifacts for review as defined within the CMS XLC Artifact Matrix. The IPT schedules and attends the AR with the BATS Board where they present the PPA for Release 1.0. Relevant system details such as business case, risks, alternatives, high level technical design, infrastructure, and security are presented using the AR template. Upon conclusion of the AR, the BATS Board approves the PRRS PPA for Release 1.0 and agrees to the systems placement into the Baltimore Data Center (BDC). Once the IPT has completed the AR, they prepare artifacts for the ISR with the ITIRB. During the AR, TRB approved PRRS ISR attendance only once during Release 1.0. The IPT attends the ISR and receives necessary funding approval from CMS Executive and top leadership within CMS to proceed with PRRS Release 1.0 and Release 1.1. Upon successful completion of the ISR, the Release Planning Phase is complete. The Scrum Team then moves into the next Agile Phase, Sprint Planning, where the user stories from the Product Backlog will be further broken down into detailed tasks within a Sprint Backlog. Sprint Planning Phase Figure : Sprint Planning Sprint Planning Phase Synopsis Sprint Planning (SpP) is held at the beginning of each Sprint Phase to select what work will be accomplished during the Sprints. Prioritized user stories that were selected from the Product Backlog during Release Planning are further broken down into detailed tasks in order to more clearly define quantities of work. Sprint Planning involves the Scrum Team in order to accurately identify how long it will take to perform each task and how much work can be accomplished per Sprint. Sprint Planning can also be readdressed at the end of a Sprint to adjust and plan for the upcoming Sprint. A is created by the Scrum Team. The Sprint Backlog contains user stories Sprint Backlog broken down into the detailed tasks the Scrum Team must address during the Sprints. The Scrum
waived in Release 1.1. Figures 9 (on page 22) and 10 (on page 23) demonstrate how, through the use of the PPA, reviews such as the AR and ISR will only occur during Release 1.0 of the project, subject to approval by the TRB. Figure : PRRS – PPA Release 1.0 Figure : PRRS – PPA Release 1.1 The PRRS IPT drafts and submits preliminary artifacts for review as defined within the CMS XLC Artifact Matrix. The IPT schedules and attends the AR with the BATS Board where they present the PPA for Release 1.0. Relevant system details such as business case, risks, alternatives, high level technical design, infrastructure, and security are presented using the AR template. Upon conclusion of the AR, the BATS Board approves the PRRS PPA for Release 1.0 and agrees to the systems placement into the Baltimore Data Center (BDC). Once the IPT has completed the AR, they prepare artifacts for the ISR with the ITIRB. During the AR, TRB approved PRRS ISR attendance only once during Release 1.0. The IPT attends the ISR and receives necessary funding approval from CMS Executive and top leadership within CMS to proceed with PRRS Release 1.0 and Release 1.1. Upon successful completion of the ISR, the Release Planning Phase is complete. The Scrum Team then moves into the next Agile Phase, Sprint Planning, where the user stories from the Product Backlog will be further broken down into detailed tasks within a Sprint Backlog. Sprint Planning Phase Figure : Sprint Planning Sprint Planning Phase Synopsis Sprint Planning (SpP) is held at the beginning of each Sprint Phase to select what work will be accomplished during the Sprints. Prioritized user stories that were selected from the Product Backlog during Release Planning are further broken down into detailed tasks in order to more clearly define quantities of work. Sprint Planning involves the Scrum Team in order to accurately identify how long it will take to perform each task and how much work can be accomplished per Sprint. Sprint Planning can also be readdressed at the end of a Sprint to adjust and plan for the upcoming Sprint. A Sprint Backlog is created by the Scrum Team. The Sprint Backlog contains user stories broken down into the detailed tasks the Scrum Team must address during the Sprints. The Scrum
XLCGuidelinesforAgileProjects.docx