One of the key traits of a Business Analyst is being able to separate the "What" from the "Why". Users of the system (and remember, stakeholder != user) generally have a pretty good idea of what they want to do, but sometimes their explanation doesn't tell the whole story. The line
User stories are a great way to manage requirements, they are small, light, to the point and make the benefit of any requirement explicit. However, just like traditional requirements, there is a skill required to 'get them right'. Below is a quick hash up of some user story mistakes. 1.