Acceptance criteria are the requirements that the product developers and product teams agree on for a specific part of their work. These requirements can be easy to understand.
Acceptance criteria are the things that a team agrees need to happen in order for work on a product to be complete.
When you make a list of the things that you want the product developers to build, be clear and concise. Write in plain language. Make it easy for them to understand what you want to be done by saying it in a way that makes sense. Talk with the developers before making this list so they know what you need from them when they do their work.
Acceptance criteria for each story or task should be verified before a product developer completes their work. The list of acceptance criteria is what you and the product team will use to tell if the work done on a product meets your requirements. If it does, then you can release it to customers.
Innovolo uses a technique called functional specification to write acceptance criteria.
Not every requirement is an acceptance criterion, so be careful not to overuse them. Acceptance criteria should only be used for what you will verify before moving on with your work. It can be easy to include too many of them and catch yourself up making sure everything is done perfectly, but then you give away all your time and energy achieving nothing.
Acceptance criteria should be prioritised as well. Only include those criteria that are the most important to the success of your product.