How do you write acceptance criteria

5 tips for good user stories

Mostly, user stories are used as the most popular technique to capture product functionality in an agile context.
The user story usually has the structure:
As < user> I want < action> to <Result> to achieve
The user story has a name, a content (short description) and some acceptance criteria. It is very difficult to write good user stories!
Here are 5 tips that can help you get better!
 1 tip: focus on the user Teams / FOCUS ON THE USER!
As the name suggests, a user story should focus on the customer, the user of the product. Write the stories from the perspective of the different users of your product: end users, corporate users, administrators, etc.
The structure: As < user> I want < action> to <Result> help you think from this perspective!
2 Tip: Writing user stories is teamwork!
The user story is not a specification! The user story must promote the dialogue between the team and customers, users and other stakeholders! It is a basis for discussion and not a substitute for dialogue! Benefit from the creativity and knowledge of the team and the stakeholders and refine the user stories in teamwork for the next sprint planning meeting.
3 Tip: acceptance - don't forget your criteria!
Acceptance criteria are what make the user story!
WHEN is the user story (US) ready, depends on the defined acceptance criteria! The user story is tested according to these criteria and is considered to be completely realized and accepted! The acceptance criteria of a US must be defined in detail at the latest when you convert the epics into smaller user stories! Beware of the wrong acceptance criteria that only repeat the story content, or hide hidden new US, or contain entire workflows! 3 to 5 acceptance criteria are a good basis for checking every product function!
4 Tip: Make your user stories simple, concise, precise and visible
Use paper card! Keep your US visible, simple, concise and precise!
Use paper cards. The paper cards are not only cheap and clearly visible, but also very good for collaboration. You can take them, write your idea on them, group them to check consistency and completeness!
* Use language that is easy to understand.
* Provide all important information about a US!
* Be careful that ambiguities do not smuggle into the US!
5 Tip: There are not only user stories!
Not everything can and should be packed in a user story!
It is not possible to formulate every single aspect of the product in a user story! Do not feel obliged to do so! For example, user interface designs are much better suited as a sketch for discussion. Use your creativity and wits to get your task done in the best way for you!
The 5 tips for better user stories as a PDF on Slideshare.
For mobile access you can simply scan the QR code
© Think-Pi Group 2020