Page History

...

• Highlight test database more. Which test environment to use to test? Hard to find, confusing.
• User Use newer version of Wiki.
• Not everyone got cutover weekend updates. Make it voluntary if interested. Sign-up roster. 
• Expected update for each step - not sure if steps 1-x done.
• Some confusion about UAT start and end dates. Then took 2 days for Lisa to do closing. Delayed due to fixing issue. Show FI close in the schedule from the start. 
• Explore what other testing can continue while close in progress. But have to keep close accurate.
• No idea what is in the enhancement packs. Didn't know it was on the Wiki.
• Send final documentation (validation steps, weekend schedule, ...) earlier.

...

• • (September - October) - Plan, create master script catalog, improve test scripts, move pending work to production
  • 10/05/2009 - Last date to implement projects until freeze ends on 12/24/2009 (Except Open Enrollment & Union Structures)
  • 10/19/2009 - Production snapshot at end of day - will be used to refresh dev & test environments 
  • 10/22/2009 - Last date to implement support & enhancement changes until freeze ends on 12/24/2009
  • 11/03/2009 - 11/08/2009 Unit Test
  • 11/09/2009 - 11/22/2009 System Integration Test (SIT Task List)
  • 11/23/2009 - 12/09/2009 User Acceptance Test
  • 12/11/2009 - 12/13/2009 Golive Weekend
  • 12/24/2009   Development Freeze ends

Wins - Schedule

•  Friday Friday noon well advertised. Worked well. Friday better than Monday.
•  Could Could compress test time, maybe cut days or a week off UAT, but current schedule allows for issues, absences. 
• Freeze period not a problem. Criticals can go during freeze.

...

•  Gill representing facilities worked.

Challenges - Other

• Steering committee IS&T heavy, business owner light. Gerry O'Toole, Wayne Turner. 
• Or Christine & Gillian are steering committee.

Steering Committee - January 20, 2009

At the end of any repeatable software exercise, it is important to review the process to determine ways to make future iterations better.  By better, we mean executing in a shorter period of time, executing with less errors or executing a greater volume. 

for For Support Pack 2009, an interview of the teams executing the Support Packs is being conducting in a group, Joint Application Development (JAD) setting.  Challenges or things that negatively impacted individuals are being captured as well as suggestions to remediate these challenges.  This list will be reviewed by the management team to determine steps to be taken to improve the 2010 experience.

Participants should brainstorm everything they felt was successful during the project life-cycle (the "Wins") as well as everything they felt could have been done more efficiently or effectively (the "Challenges") including a recommendation for remediation. This can include but should not be limited to Communications, Governance, Process, Project Mgmt, Risk Mgmt, Sponsorship, Staffing Levels, and Teamwork.

Wins - Other

• Communication
  • No paper handouts were generated during this project. Overhead presentations, emails, system messages and the wiki were effectively utilized.
  •  
• Schedule
  • Cut-over down time had no practical impact on Singapore operation.
  • The overall project and each of it's major phases were completed on time inline with the original plan.
• Governance
• Process
• Project Management
• Risk Management
• Sponsorship
• Staffing Levels
• Teamwork
• Other

Challenges - Other

• Communication
• Schedule
• Governance
• Process
• Project Management
  • Recurring nature of this project could allow for on-the-job training for future managers.  A new role (eg. project coordinator) could be defined to both prepare next year's leader.
• Risk Management
• Sponsorship
• Staffing Levels
• Teamwork
•  Other