A user story is an invitation to a conversation.
1The Three Cs
Card (a physical or digital placeholder), Conversation (discussion with the team), and Confirmation (Acceptance Criteria). You need all three for a story to be complete.
2Avoid Technical Stories
Stories should be written in the language of the user. Instead of 'Refactor the database', use 'As a user, I want the page to load faster so I don't lose interest'.
3Splitting Stories
If a story takes more than a few days to build, it's too big. Split it! You can split by workflow steps, by data types, or by simple vs complex business rules.
