Most teams are getting the hang of User Stories that have sub tasks. Unfortunately the same can’t be said about acceptance criteria.
It is so important because real user stories tell a team when the task is done.
Also Product Owners should not get heartburn because ‘obvious’ functionality was not included. All requirements should be specified in the Acceptance Criteria.
For example, Product Owners should not assume things like:
- they will get a message that says ‘no records found’ or
- the grid will support features such as pagination or sorting
They must be specified in the Acceptance Criteria if required.
There are 2 parts to getting this right. The Acceptance Criteria, then the Acceptance Tests: