INVEST in good User stories
*I*ndependent (of others stories)
*N*egotiable (not a contract)
*V*aluable (What is the business value)
*E*stimable (at least to a certain degree)
*S*mall (should fit in an interaction)
*T*estable (acceptance criteria)


Replacing The User Story With The Job Story

Summed up, the problem with user stories is that it’s too many assumptions and doesn’t acknowledge causality. When a task is put in the format of a user story ( As a [type of user], I want [some action], so that [outcome] ) there’s no room to ask ‘why’ — you’re essentially locked into a particular sequence with no context.

[Suggested job sytory]

We frame every design problem in a Job, focusing on the triggering event or situation, the motivation and goal, and the intended outcome:
When _____ , I want to _____ , so I can _____ .
For example: When an important new customer signs up, I want to be notified, so I can start a conversation with them.

Alan Klement: Replacing the User Story with the Job Story