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.

O

Role

Primary Members

Primary Responsibilities

Communication

Sponsor

Christine Meholic

  • Provide overall direction, goals & funding
  • Approve charter, scope, milestones, budget
  • Remove obstacles
  • Monthly written status report
  • Invitation to attend steering committee 1st Monday each month

Steering Committee

  1. Bart Dahlstrom
  2. Wendy Bastos
  3. Kevin
Lyon
  1. Lyons
  2. Ken Levie
  3. Gillian Emmons
  4. Christine Meholic
  • Provide oversight, schedule resources
  • Define roles & responsibilities
  • Oversight
  • Resources
  • Set standards, guidelines, processes, metrics
  • Remove obstacles, resolve issues
  • Approve go/no go decision
  • Monthly steering committee meetings - October - January
  • 10/5/2009 (Tentative)
  • 11/2/2009 (Tentative)
  • 12/7/2009 (Tentative)
  • 1/7/2010 (Tentative)

Project Manager

Ken Levie

  • Complete project on time, on budget
  • Manage overall project: planPlan, track progress, address issues, communicate

Transport Manager

TDB

  • Manage all transports
  • resolve issues, escalate when necessary, ...
  • Communicate: with project team, sponsors, steering committee, stakeholders, broader community
  • Ensure appropriate business and IS&T resources are assigned to project tasks
  • Coordinate work among project teams, data warehouse, OIS, IS&T help desk, ...

 

Transport Manager

John Tuttle

  • Define process, lists, tracking procedures
  • Plan and track effort to move pending transports to production before freeze
  • Manage any critical transports during freeze to ensure they are included in upgrade
  • Manage all transports related to support pack project

 

Core Team: Technical Leads

  1. Basis/security - Ron Parker
  2. ABAP, ITS - Wai-Ming Li
  3. Web - Rich Murphy

Technical Team

 
  • Prepare environments
  • Apply support packs
    related to support pack project * Execute SF3 modification testing; Resolve & retest issues
  • Unit test (joint with functional team)
  • Analyze & resolve issues
  • Execute cutover activities
  • Coordinate work of basis team and developers

Core Team: Functional Leads

  1. HR/Payroll - Frank Quern
  2. Financial - Mary Ellen Gearin
  3. EHS, Travel -Lee Collier
  4. Procurement (xECAT3), Facilities, Parking - Rita Zhovnirovsky
  5. ECAT3 - Elda Prudden
  6. AP, Smart - Ken Levie
  7. Functional Team

 
  1. leads - Julie Block, Bob Romanowicz, Hao Wen
  • Unit test testing (joint with technical team, track and report process)
  • System Integration Testing (integration testing (define scope, update & execute scripts), track and report progress)
  • User acceptance testing (assist if needed)
  • Serve as primary liaison with business owners
  • Analyze & resolve issues
  • Execute cutover activities
  • Coordinate work of business analysis and business owners

Core Team: QA

  1. Wendy Bastos
  2. Amanda Gilbert
  • Define & communicate process & templates to manage test cases
  • Set standards for quality assurance process
  • Oversee QA work on the project

Extended Team

  • sais-sap@mailman.mit.edu 
    • which includes all SAIS & Data Warehouse staff supporting SAP.
    • Conact Kevin Lyons, Wai-Ming Li or Bart Dahlstrom if you are not on the list and think you should be.
  • Perform tasks as directed by core team leads

Business Owners


  1. GL Reporting, JV - Magdalene Lee
  2. HR/Payroll - Scott Ball
  3. HR/Benefits - Judy Raymond
  4. Facilities - Lisa St. Croix
  5. Stockroom - Tammy Doyle
  6. EHS - Laurie Veal
  7. Spons. Billing - Doug Levie
  8. Gen AR - Donna Cairns
  9. Cashiers - Cheryl Whelan
  10. Property: Kevin Milligan
  11. Fund Centers: Peggie McGrath
  12. IST Telecom: Allan Wallace
  13. Tech Review: Jim Coyle# AP - John Larkin
  14. Procurement - Mary Bacci, John Doyle
  15. eCAT - John Doyle
  16. Travel - John Doyle, Paul Arsenault
  17. SMART - Mary Bacci, John Larkin
  18. OSP - Steve Dowdy
  19. OBO - Rob Slauzis
  • Perform user acceptance testing (define scope, update & execute scripts, retest as needed)
  • Report issues via RT
  • Train end users if any changes are discovered (none anticipated)
  • Sign-off that updated system is accepted for your business area and support packs can move to production
  • Perform any business cut-over activities
  • Validate production system (define criteria, validate system)

Business Team

 

  • Define user acceptance testing scope
  • User acceptance testing (update & execute scripts)
  • Production validation