The A.A.R.T. of Writing User Stories
Current user stories used to manage Agile requirements can be improved by clearly identifying, linking, and tracking Actors, Action, Results, and Tests. (A.A.R.T).
Writing user stories in the form of: Fred (Actor) drinks coffee (Action) to wake up. (Result) …is more clear than the traditional user story, and easier to understand and write for non-native users of English. Requiring at least one Test , written as user instruction for the Actor, increases the chances of detecting flawed requirements early.
Video producer: http://agileprague.com/