User acceptance testing is your chance to check that the software does what your business needs before you sign it off. A simple plan makes it quick and effective.

Test real tasks

Write down the ten or twenty things your team does most, and run each one through the new system from start to finish. Test with real examples, not made up ones.

Organise the testing

A little structure helps.

  • Choose two or three people who really use the process
  • Give them the task list and a place to record problems
  • Record what happened, what they expected and a screenshot
  • Sort the problems into must fix and can wait

Sign off in writing

When the must fix items are done, confirm acceptance in writing. Anything that can wait goes on a list for the next release.