As a <user or stakeholder type>
I want <some software feature>
So that <some business value>
(http://blog.crisp.se/2014/09/25/david-evans/as-a-i-want-so-that-considered-harmful)
In order to <achieve some business value>,
As a <stakeholder type>
I want <some new system feature>
or
In order to <achieve some business value>,
for <stakeholder type>
we will <some new system feature>
To get the most out of this part of the story description, you should be specific about the persona that typifies who gets the benefit of the impact that this story will make.
Use adjectives if it helps to bring the story to life, such as “busy executive”, “risk-averse investor”, “regular commuter”, “stressed mother”, “bored teenager” and so on. Avoid generic roles like “user” or “customer” – if your story benefits all users equally, then just leave out the “who” clause altogether, and save it for stories that benefit from the differentiation.
Definitely avoid using non-persons such as “the system”, “the database” or even “the Product Owner”. As Gojko Adzic once said, “The system doesn’t want to do anything – the system wants to sleep.”
I like to start with a verb that highlights the new action or behaviour the product will have, that it does not have now.
In order to <achieve some business value>,
As a <stakeholder type>
I want <some new system feature>;
Whereas <what we already have in the product>.
(http://www.cleverpm.com/2015/02/03/why-your-user-stories-suck/)
User [x] needs to [y] so that they can [z]