User Story Smells – What to avoid when writing user stories

Don`t do this when writing user stories:

Smell 1 – Everything in a Sprint should be written as a user story

Smell 2 – Stories should be sliced by technology layer, because that’s how our development team will approach them

Smell 3 – Stories don’t need acceptance criteria

Smell 4 – The product owner is a user

Smell 5 – Acceptance criteria must specify how features look & behave

Smell 6 – System-wide NFRs should be written as NFRs

Smell 7 – Specifying what the user wants is enough!

Smell 8 – User stories should be incredibly detailed

Smell 9 – User stories can depend on other stories in the Sprint

Smell 10 – Stories should be very small

Source: User Story Smells | Ryan Thomas Hewitt https://t.co/gw5Mat3ah7

This blog is a digital memory for me. I store nuggets of information, ideas and resources on these pages so that I can access and share them easily at any time, from everywhere. I always felt a strong passion for continuous improvement and that is why I am now super happy to be a professional Scrum Master. Scrum, Kanban, Agile Project Management, Coaching, Learning and Self Management are my passions and that is also what my blog is about ...

Leave a Reply