The User Story format is one practice to write Product Backlog items.
Unlike traditional requirements, the User Story is about the user, their needs, and is written at a level that is sufficient for the team to consider and deliver a solution.
The User Story should always articulate a value statement – a reason why the work is needed by the user or user type. Without a reason, the value of doing this work is unknown and so the Product Owner is not easily able to prioritise this work.
The “User” in the User Story is a person, end user, customer or persona. It’s not:
Don’t use the User Story format when:
In these cases, use other formats like: