Accurately representing the needs and responses of real life users is a key part of the product owner’s role.
-
Schedule acceptance meetings throughout the iteration, either at regular intervals or whenever a given user story is completed. Use the latest working build of the product, and exercise the functionality live.
-
Test the functionality implemented matches what is specified in the user story. Also review the user interface and user document associated with the user store if any.
-
Enter any issues in the artifact’s Comments field.
-
Update the user store artifact to reflect the outcome.
-
If a user story is accepted, change the artifact status to “Accepted” or the equivalent.
-
If a user story is not accepted, change the artifact status back to “In Development” or the equivalent, for further work. You can review it again in another acceptance meeting.
-