SAPbiz - January 13, 2009
2009 Support Pack Update Project - Lessons learned
Participants should brainstorm everything they felt was successful during the project life-cycle. This can include but should not be limited to Communications, Governance, Process, Project Mgmt, Risk Mgmt, Sponsorship, Staffing Levels, and Teamwork.
Communication - Tools that included Meetings, Emails, SAP Gui & Web messages, Conference bridge line, Status check-in line and the Project Wiki were utilized to communicate project status, roles and responsibilities and system and service outages.
Was the appropriate volume/frequency of communication provided?
Was the information accurate and complete?
What worked well? Where did you see opportunities for improvement?
Wins - Communication
Challenges - Communication
Schedule - The project schedule was primarily based on prior years experience and it's start and finish are restricted to a window that is dependent on availability of SAP packs and must be completed before the start of the new Payroll year. Although not entirely flexible, there might be some opportunities to change details within our schedule.
Could combining Systems Integration Testing with User acceptance testing become the rule vs. an option?
Could the development/transport freeze time be reduced provided process owners were available to validate and approve changes outside of the normal business hours? (i.e. nights and/or weekends)
How significant was the impact of bringing down production at noon on the Friday of the cut-over weekend?
Overview
Content Tools
Activity