1 / 4

UK R3-RAP / R3-R3 Testing Status, Issues, and Risks

UK R3-RAP / R3-R3 Testing Status, Issues, and Risks. 31st January 2007. Purpose. To present current status, risks, issues To ensure risks and issues are unambiguously understood

jamal-weeks
Download Presentation

UK R3-RAP / R3-R3 Testing Status, Issues, and Risks

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. UK R3-RAP / R3-R3 Testing Status, Issues, and Risks 31st January 2007

  2. Purpose • To present current status, risks, issues • To ensure risks and issues are unambiguously understood • To prompt a ‘cold light of day’ discussion on the implications of this not improving within current testing timelines • i.e. what if we don’t meet our own integration testing exit criteria? Draft for Discussion

  3. R3-RAP Status, Issues, Risks • Status • ITC1 exit criteria were 100% execution, 90% pass rate, reflecting that it was the last planned cycle prior to go-live. • It finished at 73% complete overall. As a result, we have gone straight into an unplanned ITC2. • Issues • EBYDOS – 19 TPR’s. Could not go live with it right now. • Risks • The level of change we will be taking through ITC2 is much greater than we would have expected at this point in time. We will not have opportunity for a final pass test on a stable version of code prior to live. • <Tim Empson able to add something here around what we are doing in looking at descoping problem interfaces until after go-live > Draft for Discussion

  4. R3-R3 Status, Issues, Risks • Status • Recall we re-planned from a 3-2-3 IT cycle strategy to a 4-4 cycle strategy to increase our ability to achieve full coverage in the test cycles. • ITC1 exit criteria were 90% execution, 80% pass rate, reflecting that it is the penultimate planned cycle prior to go-live. • We are currently at <> with a forecast position of c. 65% at the end of this week. • Issues • EBYDOS – 19 TPR’s. Could not go live with it right now. • Risks • The level of change we will be taking through ITC2 is much greater than we would have expected at this point in time. We will not have opportunity for a final pass test on a stable version of code prior to live. • <Tim Empson able to add something here around what we are doing in looking at descoping problem interfaces until after go-live. Fundamentally the message with R3-RAP is that I think we will be OK and are not in that bad shape besides EBYDOS, for which we seem to have a good contingency plan.> Draft for Discussion

More Related