Page History

...

• Communication
  •  Meeting notes maintained on the wiki pages worked well
  • Wiki very helpful for getting updated information
• Schedule
  •  Contingency  Contingency was used and needed
  •  Dedication of team and willingness to work extra hours
• Governance
  •  
• Process
  •  
• Project Management
  •  Transport  Transport Manager role useful
• Risk Management
  •  
• Sponsorship
  •  
• Staffing Levels
  •  
• Teamwork
  •  
• Other
  •  

...

• Communication
  • Meeting notes on the wiki were not always accurate
• Schedule
  • Late-occurring problem with Finance tested contingency 
  • Revise schedule to allow extra time for problems/long-duration steps
  • Schedule for preparation of different systems should reflect available resources on each system
  • Addition of enhancement packs extended time for system preparation more than expected
  • Benchmark enhancement pack application before project starts (if possible)
• Governance
  •  
• Process
  • Late delivery of high-use transactions & programs for analysis/division was difficult & time-consuming
  • Keep identification of critical transactions & reports for reference next year - include reference to test scripts
• Project Management
  • Need individual assigned to monitor issues in RT queue
• Risk Management
  • Need development & testing environments for items that must go into production shortly after go-live
  • Better definition of project freeze and difference between development freeze and transport freeze
• Sponsorship
  •  
• Staffing Levels
  • QA  could play a more predominant role i.e. back-up manager
  • Project manager should be identified earlier and have fewer testing responsibilities
• Teamwork
  •  
•  Other
  •