The purpose of User Acceptance Testing (commonly called UAT) is to get sign-off by the end product owner for a milestone delivery. This can be an internal sponsor or actual end users of the solution. The acceptance of the deliverable signifies when a goal is reached. In football this is the Ref calling a touchdown!
2-10 depending on the size of the team. If it becomes larger than 10 people consider breaking out into smaller groups.
30-60 Minutes. No one wants to be in a meeting longer than needed. Try to keep it short and sweet.
Practitioner to Master. It may take some practice to run this play.
Prior to this play you will need to have a clear acceptance criteria defined. This should have happened during the Defining Requirements play or in the Creating Specifications play. If not, do so now.
The right people are key to the success of this play. Review the invite list to ensure that all the various experts are in the room.
Virtually or in-person it is critical that everyone has face-time with each other. So make sure that if attending virtually that everyone can connect in video chat. You will also need to share ideas, so a whiteboard is important and a space that fosters creativity and innovation.
All of our plays are five steps or less! However, you may need to run multiple plays to get the most out of this one. Don’t worry – you can do it! Learn the play, rehearse it regularly, apply it in the field and debrief on the outcomes. If it worked well, use it again; if it didn’t, find out why. Are there new factors in the system you need to consider, or do you just need to keep practicing? If you need help or have questions on this play, contact us!
We are sorry that this Play was not useful for you!
Let us improve this Play!
Tell us how we can improve this Play?