User Story or Stakeholder Story?
via Scrum.org Blog by Krystian Kaczor
User Story is the most widely used Agile Practice for capturing needs and requirements and describing Product Backlog Items. For some time I wonder if the name of the technique might be somewhat limiting. The focus sometimes is too much on using the proper technique and we lose the whole purpose of using User Story.
The purpose of using User Story is to capture natural conversation about what needs to be built in the product from the user point of view. It should provoke or later capture conversation between the one who wants the feature and the one who will build it. The key is to understand the intention and create the best possible solution with the known boundaries of architecture and technology. When Development Team understands why the user wants it and what the user wants to achieve they can come up with a set of possible solutions.