ppt and uat programme management briefing pack n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
PPT and UAT Programme Management Briefing Pack PowerPoint Presentation
Download Presentation
PPT and UAT Programme Management Briefing Pack

Loading in 2 Seconds...

play fullscreen
1 / 11

PPT and UAT Programme Management Briefing Pack - PowerPoint PPT Presentation


  • 578 Views
  • Uploaded on

PPT and UAT Programme Management Briefing Pack. Alison Arnold / David Rowe 13 November 2002. In this briefing pack we will…. Review current timelines for PPT, UAT and implementation Discuss the team organisation that will deliver PPT and UAT

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'PPT and UAT Programme Management Briefing Pack' - chambray-braun


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
ppt and uat programme management briefing pack

PPT and UAT Programme Management Briefing Pack

Alison Arnold / David Rowe 13 November 2002

in this briefing pack we will
In this briefing pack we will…
  • Review current timelines for PPT, UAT and implementation
  • Discuss the team organisation that will deliver PPT and UAT
  • Look at communication and status reporting during this phase
  • Suggest some suitable test metrics and exit criteria for UAT and PPT testing
  • Provide an update on UAT progress
slide3

Consolidated UAT + PPT Execution Plan

Track A – Normal plus Christmas Break plus additional two week delay

Version 6.0 13/11/02

Volume refresh

Volume refresh

DR

DR

4/11

11/11

18/11

25/11

2/12

9/12

16/12

23/12

30/12

6/1

13/1

20/1

27/1

3/2

10/2

17/2

24/2

3/3

10/3

17/3

24/3

31/3

System test cycle 3/4

V

PPT readiness activities: Tech Arch

Performance

Implement sorter code: AS

test

Sorter and RDM tests: AS + Logistics

Xmas

Implement release 3c: AS, Tech Arch, DK

User validation: Odyssey users

Version control tests: AS, Tech Arch

V

Implement release 4a to Max volume: AS, Tech Arch, DK

Go Live

29/30th

March

User validation: Odyssey users

Batch step by step – first half

RMS data set up - Odyssey users

Normal batch run AS

Parallel run 1

Sorter / RDM tests: AS + Logistics

Implement 3c and 4 with pilot

Sorter

RDM

Live

V

Normal batch run AS

Parallel run 2: Odyssey users including Volume of users

Go Live Prep

Contingency

Expected Use of Contingency

ppt and uat execution organisation

ODYSSEY

GOVERNANCE

PROGRAMME

MANAGEMENT

TEST PHASE

LEADS

PPT and UAT - Execution Organisation

Steering Committee

Neil Kinlay

Matt Stringer

John Gahagan

Helen Brunt

Iain Winskill (Execution Controller)

Alison Arnold

Gillian Kingston

David Rowe

Gillian Kingston

(Execution lead)

John Pryor

(Execution lead)

EXECUTION

John Peat, Sam Gray, Simon Bates, Bob Northam, Richard Hemmings, Martin James, Merv Scarlett, Mike Pearson

Business testers

Odyssey testers

SIR MANAGEMENT

Mick Connell Val Fry

John Peat, Sam Gray, Simon Bates, Bob Northam, Richard Hemmings, Martin James, Merv Scarlett, Mike Pearson, Chris Butt, Stuart Smith, Xing

IF/RMS/RDF/RDM analysis/fix

Legacy fix

Dave McGrath (L) Legacy fix team

ON SITE FIX

Teresa Day

Data conversion fix

Karl Hawkins (L) Danny Kelly

Damian Hedley

Peter Rogers

Technical Architecture fix

Steve Wood

Panacea

OFF SITE FIX

IBM

Accenture

Galleria

BT

AIM

Retek

CA

Cleco

SeeBeyond

Oracle

Fujitsu

ppt and uat communications channels
PPT and UAT Communications Channels

As with other phases of testing a number of formal communications channels will be used to review progress and manage issues.

test phase metrics and reporting
Test Phase Metrics and Reporting
  • The metrics used for UAT and PPT will be similar to those used throughout testing and will measure:
  • Progress in test execution (split by UAT/PPT):
    • at phase level: are we entering end exiting each phase according to plan
    • within a phase: are we completing the scheduled tests within each phase
  • SIR hotspots (aggregated for both tests):
    • current status of open SIRs by application and priority
  • SIR raising, fix and closure (aggregated for both tests):
    • measure the rates at which SIRs are being raised, fixed and closed
  • Projected end date:
    • Use best information from all available measures to extrapolate likely completion date for testing and subsequent implementation
  • A commentary and RAG status will summarise key areas of progress as well as the major issues that
  • are impacting current progress and those that may have a subsequent impact on go-live.
  • The proposal is to continue to use the existing reporting pack layout.
test phase exit criteria
Test Phase Exit Criteria
  • As in previous test phases exit from PPT and UAT will be based on :
  • Successful completion and sign off of all scheduled tests
  • Prevalence and impact of unresolved SIRs
  • Given the proximity to go-live the targets set on these measures will be necessarily more
  • severe than preceding test phases:
  • Outstanding SIRS:
  • No critical or high priority SIRs. These are SIRs that would either prevent go-live or require a substantial and complex workaround
  • Minimal number (< 5% of SIRs raised in system test and PPT phases) of open high, medium or low priority SIRs. Every open SIR must have either:
      • a documented and agreed short-term workaround or
      • a documented and agreed resolution, resolution date and regression test slot
  • There will be some (generally cosmetic) SIRs that we will do nothing about prior to go-live
  • Test completion: Each test will be assigned a RAG status:
uat update objectives
UAT Update - Objectives
  • Check that key processes work end to end
  • Check that all financial reporting is correct
  • Check that the volume of transactions keyed by users is manageable
  • Check the integrity of data coming out of conversion
  • Check key contingencies (e.g. ranging, local books)
  • Involve Odyssey and non-Odyssey users
uat update key activities for the next month
UAT Update – key activities for the next month

11/11

18/11

25/11

02/12

Confirm user group

Request access to all required test environments

Confirm application requirements for UAT

USERS

Confirm user skill set and supplementary training

Schedule additional training for users

Confirm availability of desk area, power and network connectivity

Schedule PC moves in for w/c 2/11

Requisition additional test PCs of required spec

Request user access for all required test systems under user’s own ids

LOGISTICS

Sign off scenarios

Complete approach

Drill down on scenarios to define

conditions

Script phase (cycle) 1 tests

Build cycle 1 execution plan

Define data reqs for cycle 1

TEST MODEL

Script phase (cycle) 3 and 4 (phase 2 less critical)

Define data requirements for cycles 3 and 4

Data setup

Build cycle execution plan for

cycles 2,3,4,5,6