Page History

...

1. Unit Test Schedule? - SF3 Upgrade will not complete until this evening & SF2 by tomorrow evening or Wednesday morning. - Impact?
   •  Update to SF3 should be completed tonight by 10:00pm.
   • SPAU - generate tonight. 
   • Tomorrow am.  Rich K. will apply SAP notes. Should take 2hrs
     • When can SPAU & action log activities begin? - Other prep. activities? (interfaces, queued data files, etc.)
       • Mods and SPAU also will start Tuesday a.m. and complete by 3:00 pm 
     • How many days are required for UNIT test / from where in the plan do we subtract the time?
       • The project plan's schedule can not be changed. We must complete unit testing by Monday 11/9.
       • SF2 will be available for testing on Wednesday by aproximatly 11:00 am
2. Unit test execution SF2
   • SF3 was offered as an alternative environment to begin unit testing however the prep.(i.e. authorizations), results logging, and issue resolution were reasons to keep unit testing confined to one system.
   • SF2 update should be completed by late Tuesday or early Wednesday (8:00 a.m.)
   • A Check-in with the core team is scheduled for Tuesday at 3:00 to confirm we are on track.
   •  Wednesday a.m. activites for SF2:
     •  Transports from SPAU work, BSI transports ~1hr#* **{*}The action log will be executed (1 - 2hrs)*
     •  Unit test start - 11am Wednesday (original scheduled to start Tue 8am - planned duration was 5 days has now been cut to 3 days)
       • Consolidated list will be split up by teams.  Each team will update their spreadsheet with Pass/Fail Results
       • Daily updates required - If updated spreadsheets can not be posted to the Wiki daily, a percentage complete should be communicated to the PM and the end of each day. Core team check-in meetings are scheduled for 3:00 PM. on Wed., Thur., & Fri this week. The plan is to test on Saturday unless status for each group is on target to completed on time without weekend testing.
       • Issues/Errors must be logged in the SAP:: Test Issues queue, email = saptest@help.mit.edu.
       • The spreadsheets will be the official test log - Results (pass/fail) and testers name must be filled in for completion of this test phase
3. Time Sheets
   • There is a steering committee mtg this Wednesday
   • We need to stay current with our time allocated to this project
   • confirm that SAIS project team members have project related tasks assigned in Daptive
4. Testers
   • SAIS should have their same authorizations in SF2. Let, Ken know if there are additional authorizations needed.
   • We are looking for the complete list of business testers for UAT and the names of those who would need to be unlocked for SIT.
5. December 24th Institute holiday - was to be the 1st day for resuming normal transports. Can this change to the 23rd?
   •  Freeze will be lifted 12/29 due to institute closing on 12/24. Payroll pension 12/22, Weekly is 12/22 & Monthly 12/23 we will consider transports for the 22nd only if there is a pressing reason.

...

• Background
  • Why do we do this?  - "Because we have need to!"
    • HR/Payroll year end support packs are released at this time each year and must be applied before the up coming year's Payroll run.
    • This is opportunity to bring other support pack levels up to date
      • SAP recommends that our support pack level be current
    • We become more efficient and more effective organization in testing
  • What's new?
    • The addition of Enhancement Pack 4 & Basis Enhancement Pack
  • Lessons learned
  • SF2 Development Environment Support & Enhancement Packs were applied and pre-processing steps completed on 11
    Progress to date:
    • • Freeze date confusion - Production developmant freeze period (10/5/09
      Unit Testing completed on 11/7
      • through 12/29/09
      • )
        • December 24th Institute holiday - was to be the 1st day for resuming normal transports. Can this change to the 23rd?
        •  Freeze will be lifted 12/29 due to institute closing on 12/24. Payroll pension 12/22, Weekly is 12/22 & Monthly 12/23 we will consider transports for the 22nd only if there is a pressing reason.
  • • • Communication - Wiki  https://ssit-docs.mit.edu/display/sapscripts/2009+Year+End+SAP+Support+Pack+Project^{Image Added}
      • Project go-lives too close to freeze dates
      • Test scripts & Test Plans
  • Progress to date:
    • SF2 Development Environment Support & Enhancement Packs were applied and pre-processing steps completed on 11/5/09
    • Unit Testing completed on 11/7/09
    • Issues - 16 logged issues 
      • 2 severe - defect is to critical business process that impacts a majority
      Issues
      • 16 logged issues  2 severe - defect is to critical business process that impacts a majority of system users 
      • 5 high - defect is to critical business process that impacts a specific business area or function 
      • 2 medium -defect is to either a non-critical function or alternative processes exist 
      • 7 low - defect may not be attributed to support pack updates and/or can not be reproduced
    • SH2 SIT Environment has been updated as 11/10/09
      • A snapshot of production, as of 10/19/09 was applied to this environment 
      • Data warehouse extracts have been completed
      • Trial balance has been executed 
  • Schedule - Next Steps
    • Run Payroll
    • Unlock Testers
    • Begin SIT Testing

  • November

    November 2009

  Monday	Tuesday	Wednesday	Thursday	Friday
  2 SF2 UNIT TEST	3 SF2 UNIT TEST	4 SF2 UNIT TEST	5 SF2 UNIT TEST	6 SF2 UNIT TEST
  9 SIT	10 SIT	11 HOLIDAY	12 <SAPbiz> SIT	13 SIT
  16 SIT	17 SIT	18 SIT	19 SIT	20 SIT
  23 UAT	24 UAT	25 <SAPbiz> UAT	26 HOLIDAY	27 HOLIDAY
  30     UAT
  December  2009
  Monday	Tuesday	Wednesday	Thursday	Friday
  	1 UAT	2 UAT	3 UAT	4 UAT
  7 UAT	8 UAT	9 UAT	10    Go / No Go	11 PS1 DOWN      AT 6PM
  14 PS1 UP AT ???	15	16	17	18
  21	22	23	24 HOLIDAY	25 HOLIDAY
  28 SH2 OPEN FOR GENERAL  TESTING	29	30	31 HOLIDAY

  ...