Page History

...

Including more detail on the Action Log and implementation plan than in the past
Everyone stepped up to meet the shortened deadlines by working extra hours but this shouldn't become a habit
Second year of SIT execution
Now have two years of SIT scripts
Some business owners / users updated scripts on their own
Aliases worked well again this year

...

Implement the support packs and enhancements in a sandbox/prototype environment first to get a better idea of the impact and time needed
Start review/analysis of the support packs already received earlier - don't perform testing until all are received
A A spreadsheet is not the best tool for keeping the information needed for testing; a DB or other tool would be helpful
Have an environment with the changes applied available so development can continue
During During the implementation, please don't move status calls earlier without at least an hour's notice
Extended team meetings were not conducted frequently enough
Information dissemination was pushed down to the individual functional teams, didn't come from one place
Many individual test scripts still not updated
I had responsibility for approving UAT for some business areas due to staff turnover
Confusion about when UAT ended
Confusion about what could be tested during period end closing
Confusion about the intention of SIT / UAT
Business owners were told they did not have to test during UAT; they could accept the results of SIT as UAT; created a mess that had to be re-communicated at length
Not enough communication
Scheduling of users during UAT wasn't done consistently; given a time period and a deadline and told to meet it; created lots of uncertainty around the deadline

Space shortcuts