User Story format

New types of user stories = job stories;

When < situation >, I want to < action > so I can < goal >

• This is better than classic user stories because it does not depend on a type of user. It may encompass many different users/personas who want to accomplish the same thing
• It is situational
• The user or persona can be inferred and their identity doesn't actually matter that much

Old types of user stories:

As a < type of user >, I want < some goal > so that < some reason >

• Emotional journey

• Include perspectives of adjacent Users

• ✍️ Extra tips for writing User Stories

Acceptance Criteria

• Acceptance criteria will be added to shorter user stories in the backlog
• Acceptance criteria should prevent any further questions about task scope or requirements
• Acceptance criteria make it clear what's needed and how to test it

Given a < user > is < in a scenario/context > When they < perform a specific action > Then < something should happen> And then < a second thing should happen > Unless < some other condition with an exception >