How many of you recognize the situation: Couple of first days of acceptance testing are spent with battles with basic information, integrations and installations. Few things are not where they should be. First 10-20 defects are not in fact defects, but are caused by poor preparation. This is how 25-50 hours of good testing time is wasted away.

You probably have a list of your own goals for acceptance testing. I have focused our goals in these two:
Goal 1 = To make sure, that the project execution compliments the requirements of the business and is suited for the business execution specifications.
Goal 2 = The implementation has no negative effect on business.
Because the goal is to ensure successful implementation, it needs to be tested first. Implementation exercise is a good way to do it. Simple, but effective method goes like this:
Before starting acceptance testing:
In the beginning of the acceptance testing the implementation is simulated

There are easier ways to plan implementation than by doing a large Excel sheet. Easy to use tools, that help with the planning and managing implementation, do exist. With the right methods, implementation plan is created in a way that makes executing implementation exercise easy.
The most common reason not to do right things at the right time is hurry.
”There’s never enough time to do it right the first time, but there’s always time to do it over”.
Download a guide on software testing in development projects. You’ll avoid many common mistakes and succeed in the implementation.
Improved testing efficiency, 70% less emails and real time reporting
Easily plan and execute even the most challenging development project