August 31, 2009 Core Team

Agenda

Deliverables due this week:

• Finalize refresh, snapshot, landscape plan - Ron & Frank (including SH2 plans)
• Confirm business owners - Rita, Mary Ellen, Lee, Frank, Ken
• Detailed project plan - Bart (including enhancement packs)
• Add team to daptiv project - Bart
• Appoint transport manager - Kevin, Bart
• Unit test preparation - 1) Create list of frequently executed transactions - Ron; 2) Following week - list of unit tests & assignments - Functional Leads
• SIT preparation - 1) Complete test catalog of all scripts - complete 9/4. 2) Verify test scenarios include all new, critical functions - destermine target date based on detailed project plan. 3) Review existing scripts for obsolete items to be deleted 4) validate with business. 

Completed last week(s):

• High level schedule
• Teams, roles, responsibilities
• Core Team kick off
• Created Daptiv project request

Open Issues:

•  Determine web infrastructure update plan - September 15. Rich.

September 14, 2009 Core Team

Agenda

Status of deliverables from August 31 meeting:

• Refresh, snapshot, landscape plan - Ron & Frank (including SH2 plans) > Ron: By Thursday 9/17/2009.
• Business owners - Rita, Mary Ellen, Lee, Frank, Ken > Done
• Detailed project plan - Bart (including enhancement packs) > not complete. By Thursday 9/17/2009.
• Add team to daptiv project - Bart >
  • Individuals added to tasks where resource managers have assigned individuals.
  • Wai-Ming, Ron, Julie: pls assign names to daptiv resource request.
• Appoint transport manager - Kevin, Bart > not complete.
• Unit test preparation -
  • 1) Create list of frequently executed transactions - Ron; > Complete. Bart to post on wiki
  • 2) Following week - list of unit tests & assignments - Functional Leads > not complete.
• SIT preparation -
  • 1) Complete test catalog of all scripts - complete 9/4.
    • Hyperlinks - have to find doc & relink - see Wendy for instruction on mechanics. Add details by today to wiki.
    • Lee, Rita (can't link), Elda, Ken, Mary Ellen - not done > By Thursday 9/17/2009 at latest.  What has to be done, plan for each area, status of catalog, test scripts - add detail to wiki.
  • 2) Verify test scenarios include all new, critical functions - determine target date based on detailed project plan. > of by Thursday 9/17/2009.
  • 3) Review existing scripts for obsolete items to be deleted > part of 1).
  • 4) validate with business. > later, after SAIS work is complete.

Due this week:

• Complete overdue items from August 31 list
• Pending transports: 1) move to production before 10/22 or 2) mark as obsolete/delete, or 3) define schedule to complete dev, test, production . Priority to work in test. List from Ron by Friday.

Open Issues:

•  Determine web infrastructure update plan (Oracle Application Server update) - September 30. Rich.

September 21, 2009 Core Team

• Transports
  • John Tuttle - transport manager
  • Pending transports will be posted to wiki today
  • 1) move to production before 10/22 or 2) mark as obsolete/delete, or 3) define schedule to complete dev, test, production .
• Transaction / report list
  • Attachment on script catalog page
  • Functional / technical leads complete columns e, f, g, h this week (team, custom, unit test scope, assignee)
• Test catalog updates
  • AP - complete.
  • HR/Payroll (incl EDI)- not complete. Adding 25 from past year.
  • FI - not complete. Adding last year items, travel
  • Purchasing, Parking, Stockroom, Facilities - complete
  • SMART - complete
  • EHS - complete
  • Ecat, purchasing EDI - complete
  • Data warehouse - Scripted? Wendy follow-up. Incl. extracts from other catalogs to be tested in SIT. Functional leads tell data warehouse which tests will be included.

September 22, 2009 SAPbiz

Agenda

1. Background
2. Some Lessons Learned from 2008
   • Freeze date confusion
   • Project golives too close to freeze dates
   • Test scripts
   • Roles, teams
3. Teams, roles, responsibilities
4. Schedule
5. Test plans
6. Questions?

September 28, 2009 Core Team

Agenda:

1. Test plans, scripts, catalogs
   • Unit test - see script catalog page attachment of transactions & reports. Recommend an access database for next year. Complete updates by 10/9/2009. Then Bart will merge separate sheets.  Also, see data warehouse notes on test script page.
   • System integration test - All complete except Finance. Each SAIS functional lead to verify that interfaces & data warehouse tests are included in test scripts and/or scenarios for their area.
   • User acceptance test - SAPbiz discussion & follow-up. 'Do not duplicate tests' not a rule, its a guideline. Users invited (encouraged) to participate with SAIS in system integration testing. But business owners still have to sign off. Team members to update wiki test script page to clarify anything not clear regarding test phases. SAIS functional leads to meet with business owners and document UAT plans on this wiki before testing starts in November. Approach to UAT may differ by business area, but requirement is to do whatever is required for business owner sign-off.
2. Transport management will be discussed at 10/5 core team meeting.
3. Other
   • Bart to schedule kick off for extended team - late next week.
   • Send wiki updates to extended team weekly.

October 5, 2009 Core Team

Agenda:

1. Transport management
2. Plan review
3. Other
   • Extended team kickoff Thursday 10/8 10:30-11:30 Back Bay A&B
   • Unit test spreadsheet updates due Friday 10/9/2009

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

Agenda:

1. Some Lessons Learned from 2008
   • Project wiki
   • Freeze date confusion
   • Project go-lives too close to freeze dates
   • Test scripts
   • Roles, teams
2. Progress to date:
   • Teams, Roles, Responsibilities
   • Schedule & Plans
   • Test plans
   • Kick off meetings, weekly core team meetings
3. Budget
   • This year's project IS&T Budget 3500 hours; $240K. Actuals thru September not complete.
   • Last year's project IS&T Actual 3105 hours
   • Increase in this year's hours to continue test script updating, organizing.
4. Risks & issues
   • Travel Project go-live has been delayed 1 week - If changes are required there could be an impact on resources and SAP environment consistency. (Mitigation would be to suspend pilot until January '10)

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
   - Approach to remaining, pending transports
   - How to handle criticals during freeze
2. Basis
   - SF3 trial run results
   - SAP release of support packages
3. Developer tasks planning - SPAU, ...
4. Unit test
   - Consolidated spreadsheet available
   - Assign an individual to each test
5. Other

October 26, 2009 Core Team

November 2, 2009 Core Team

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