User Story

A user story tells a short story about someone using the product.

Note that user story is written from the perspective of a user. Many times we miss out this context and write user stories according to perceptive of developers.

In user story there is not much detail to actually implement the behavior required. User story represents a conversation that is yet to occur between the development team and the customer.

When developer picks up the story, developer discusses with customer and talking through requirements in details. This is more of analysis, understanding and clarification. This analysis phase will in turn provide several acceptance criteria that will determine if the story is deemed complete.

After gathering requirements, developer has to propose the any design changes and use tools like visio and UML diagrams to communicate any changes or new additions. It is then generally followed by breaking user stories in to tasks and work towards implementing them to meet the acceptance criteria.