Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

Key dates

Support Pack Project

  • Now - October - Plan, create master script catalog, improve test scripts, move pending work to production
  • 10/05/2009 - Last date to implement projects until freeze ends on 12/24/2009 (Except Open Enrollment & Union Structures)
  • 10/19/2009 - Production snapshot at end of day - will be used to refresh dev & test environments 
  • 10/22/2009 - Last date to implement support & enhancement changes until freeze ends on 12/24/2009
  • 11/03/2009 - 11/08/2009 Unit Test
  • 11/1609/2009 - 11/2922/2009 System Integration Test (SIT Task List)
  • 11/3023/2009 - 12/09/2009 User Acceptance Test
  • 12/11/2009 - 12/13/2009 Golive Weekend
  • 12/24/2009   Freeze ends 

Summary Plan

Image Removed

 Current Detail Plan

  • Development Freeze ends

Open Enrollment & Union Structures

  • 09/15/2009 - 10/01/2009 System Integration Test
  • 10/01/2009 - 10/31/2009 User Acceptance Test
  • 11/02/2009 - 11/06/2009 Pilot Open Enrollment
  • 11/09/2009 - 11/20/2009 Community Open Enrollment
  • 12/06/2009   Vendor Extracts

Summary Plan

Image Added

Monthly Priorities & Deliverables

 

Month

Major Deliverables

Responsible

August

  1. Plan, resources, kickoff
  2. QA instructions, templates
  3. Test scope defined
  4. Consolidated master test catalog
  1. Bart
  2. Wendy
  3. Core Team - Functional / Wendy
  4. Core Team - Functional

September

  1. Pending work moved to production
  2. Updated test scripts
  1. Core Team - Functional
  2. Core Team - Functional

October

  1. System preparation
  1. Core Team - Technical

November

  1. Unit Test
  2. System Integration Test
  1. Core Team - Technical/Functional
  2. Core Team - Functional

December

  1. User Acceptance Test
  2. Production
  1.  Business Owners
  2. All

Detailed Plan

2009 Support Packs - Detailed Plan.mpp

The 10/19/2009 snapshot will be used because (1) it stages time data after it has been loaded but before it has been evaluated, (2) it is right before the execution of the monthly pension run, (3) it is before the monthly feeds for the regular monthly payroll, (4) it is also the closest date to the freeze so it should minimize the number of transports that will need to be tracked and imported into the refreshed environments. (Notice the heavy slant towards HR/Payroll testing - but it should work fine for the other functional areas.)

...