August 31, 2009 Core Team

Agenda

Deliverables due this week:

Completed last week(s):

Open Issues:

September 14, 2009 Core Team

Agenda

Status of deliverables from August 31 meeting:

Due this week:

Open Issues:

September 21, 2009 Core Team

September 22, 2009 SAPbiz

Agenda

  1. Background
  2. Some Lessons Learned from 2008
  3. Teams, roles, responsibilities
  4. Schedule
  5. Test plans
  6. Questions?

September 28, 2009 Core Team

Agenda:

  1. Test plans, scripts, catalogs
  2. Transport management will be discussed at 10/5 core team meeting.
  3. Other

October 5, 2009 Core Team

Agenda:

  1. Transport management
  2. Plan review
  3. Other

October 7, 2009 Steering Committee 9-10am W92-240 Riverside

Agenda:

  1. Some Lessons Learned from 2008
  2. Progress to date:
  3. Budget
  4. Risks & issues
  1. #* Application of separate support and enhancement packs together. risk = more notes having to be applied over a 2 day weekend may be tight (this strategy has been employed at Lincoln Lab due to the benefit of lowering the cost of repeating this effort if note were applied at different times.) The enhancement notes are to functions the MIT is not currently using, therefore propose low risk of impact. 
  2. Other

October 8, 2009 - Extended SAIS team Kickoff 10:30-11:30 W92-Back Bay

Agenda:

  1. wiki - source of all information
  2. Teams, roles, responsibilities
  3. Schedule
  4. Landscape
  5. Transport management
  6. Test plans
  7. Questions?

October 19, 2009 Core Team

Agenda:

  1. Transports
    - Freeze starts this Thursday 10/22
    - Approach to remaining, pending transports - if there are any requests to move transports in sync with support pack updates that are unrelated to support pack fixes, we will review/approve these requests at our core team weekly meetings
    - How to handle criticals during freeze - use normal process + support pack process / queues - generate your RT ticket in the appropriate functional area queue and after your transport is approved as critical, enter a second RT ticket in the SAP:: Test Issues queue, email = saptest@help.mit.edu
  2. Basis
    - SH3 trial run results w/ enhancement pack 4. Decision no later than next week.
    - SAP release of support packages - on 10/15 as scheduled. Stack 16 for ECC600
  3. Developer tasks planning - SPAU, ... in SF3. Enhancement framework strategy. Wai-ming - Lead & schedule meeting. 
  4. Unit test
    - Consolidated spreadsheet available
    - Y w/ blank team responsible > Ken create one list of 430 & TBD, each team update; any other changes to master coordinate with Ken. All master sheet updates done by Ken. Complete by Friday.
    - Assign an individual to each test
    - Decide on TBD 'Test during unit test'

    Test during Unit test? Y/N/TBD

    Y





















    Count of Test during Unit test? Y/N/TBD

    Team Responsible (HR/PY; Fin; EHS; Logistics; ABAP; Basis)

     

     

     

     

     

     

     

    ABAP

    Cross App

    EHS

    Fin

    HR/Payroll

    Logistics

    Logistics/Fin

    Logistics/HR

    (blank)

    Grand Total

    Total

    42

    3

    16

    291

    256

    199

    2

    4

    430

    1243

October 26, 2009 Core Team

  1. Status Updates for Project Plan -
    1. - SH3 practice update- complete 10/16 (done)
    2. - PS1 snapshot for SH2- taken 10/19 (done)
    3. - SFK kernel update - complete 10/19 (done)
    4. - SFK oracle upgrade - complete 10/19 (done)
    5. - Pull & store DW extracts - 10/20 (done)
    6. - SFK support packs - start 10/26 (dates require change) Questions regarding  system downtime and when the earliest we can start SF2 update. Can not begin until after open enrollment transports  are applied. Question for Julie is if Tuesday is an option? Unit testing would start on the 11/3. If we can not begin unit testing on 11/3 it would be prefered that we take time needed away from SIT.
  2. Unit Test - Waiting for team updates - decide how to use spreadsheet for logging results - All updates have been made to the exception list of 430+. Ken will make the changes to the consolidated spreadsheet. The plan will then be to split the list up by team for execution of the Unit test.
  3. Transports - We are currently in development freeze -
    1. - Critical transports
    2. - Synchronzed transports (i.e. Open Enrollment)
    3. - Pending transports - List?
  4. Developer Planning Meeting - Wai Ming - Status - Since there is only ONE day allocated for the MOD in SF3 and we are running a very tight schedule, we will NOT move any MOD to the Enhancement Framework in the Support Pack 2009 project.
  5. SAPbiz this week - Message regarding user participation in SIT

October 28, 2009 SAPbiz

Agenda

  1. Background
  2. Some Lessons Learned from 2008
  3. Teams, roles, responsibilities
  4. Schedule - Important Dates
  5. Transport Control Procedure
  6. What next?
  7. Questions?

November 2, 2009 Core Team

  1. Unit Test Schedule? - SF3 Upgrade will not complete until this evening & SF2 by tomorrow evening or Wednesday morning. - Impact?
  2. Unit test execution SF2
  3. Time Sheets
  4. Testers
  5. December 24th Institute holiday - was to be the 1st day for resuming normal transports. Can this change to the 23rd?

November 4, 2009 Steering Committee 9-10am W92-240 Riverside

November 9, 2009 Core Team

November  16, 2009 Core Team

November 23, 2009 Core Team

November 30, 2009 Core Team

December 7, 2009 Core Team

December 9, 2009 Steering Committee 9-10am W92-240 Riverside

Agenda:

  1. Go / No Go decision
  2. Golive plan 12/11-12/13
  3. Post-golive support plan 12/14

December 14, 2009 Core Team

Agenda:

  1. Production issue triage (if any)

January 11, 2010 Steering Committee 9:30-10:30 W92-240 Riverside

Agenda:

  1. Lessons Learned