13 17 As a User, I want to have the ability 5 A user can sign-up for to sign-up for email updates so that email updates. I know the latest information 1.1 pertaining to the website. 14 9 As a User, I want the system to be 20 The website is compatible mobile device compatible so that I with mobile devices, Release (Tentative) can access the system remotely on a PDAs and tablets. phone, PDA or tablet. 15 10 As a User, I want to be able to 13 End user feedback and provide feedback and ratings on ratings about Providers Providers to increase transparency can be captured on the for users. website. 16 11 As a Product I want to have 8 Feedback can be reviewed the ability to approve user feedback and vetted prior to being prior to online posting to ensure posted online. appropriate nature of the content. 17 12 As a Product Owner, I want the 20 Web analytics are being capability for system analytics and captured and can be reporting so that I can analyze site viewed and analyzed. traffic and activity. Continued… After estimating Scrum Team velocity, Scrum Master Jason and the team determine that five Sprints will be required for Release 1.0 in order to adequately implement the user stories. Each Sprint will be a time boxed four week duration. To achieve end to end product integration, a 6th integration testing Sprint of four week duration is added. This gives the Scrum Team six months to complete Release 1.0. Since each production release is defined by the XLC as an independent IT project, both releases require a separate PPA. A preliminary PPA is drafted for Release 1.0 which identifies that PRRS will be a Complexity Level 3 project because it is a new system, introduces new business process models, and contains significant data and interface complexity. Preliminary artifacts, as identified within the CMS XLC Artifact Matrix, are also begun by the IPT ahead of the first XLC gate, Architecture Review (AR). PRRS plans to attend AR only once during Release 1.0, as the business architecture will not change for Release 1.1. Therefore, the IPT plans to waive the AR for Release 1.1. This waiver request will be justified within the Release 1.1 PPA that will be prepared during the next release planning meeting. Similarly, since funding for PRRS will already be secured, the ISR will be
Release 1.1 (Tentative) 13 17 As a User, I want to have the ability to sign-up for email updates so that I know the latest information pertaining to the website. 5 A user can sign-up for email updates. 14 9 As a User, I want the system to be mobile device compatible so that I can access the system remotely on a phone, PDA or tablet. 20 The website is compatible with mobile devices, PDAs and tablets. 15 10 As a User, I want to be able to provide feedback and ratings on Providers to increase transparency for users. 13 End user feedback and ratings about Providers can be captured on the website. 16 11 As a Product I want to have the ability to approve user feedback prior to online posting to ensure appropriate nature of the content. 8 Feedback can be reviewed and vetted prior to being posted online. 17 12 As a Product Owner, I want the capability for system analytics and reporting so that I can analyze site traffic and activity. 20 Web analytics are being captured and can be viewed and analyzed. Continued… After estimating Scrum Team velocity, Scrum Master Jason and the team determine that five Sprints will be required for Release 1.0 in order to adequately implement the user stories. Each Sprint will be a time boxed four week duration. To achieve end to end product integration, a 6th integration testing Sprint of four week duration is added. This gives the Scrum Team six months to complete Release 1.0. Since each production release is defined by the XLC as an independent IT project, both releases require a separate PPA. A preliminary PPA is drafted for Release 1.0 which identifies that PRRS will be a Complexity Level 3 project because it is a new system, introduces new business process models, and contains significant data and interface complexity. Preliminary artifacts, as identified within the CMS XLC Artifact Matrix, are also begun by the IPT ahead of the first XLC gate, Architecture Review (AR). PRRS plans to attend AR only once during Release 1.0, as the business architecture will not change for Release 1.1. Therefore, the IPT plans to waive the AR for Release 1.1. This waiver request will be justified within the Release 1.1 PPA that will be prepared during the next release planning meeting. Similarly, since funding for PRRS will already be secured, the ISR will be