Gathering Requirements through User Stories in Vocabulary Explanation Accelerator – By Sergio Santilli & Andrew Li
Software requirements is a communication problem, those who want software solutions, must communicate with those who build it.
To capture a description of a software feature or requirements, from an end-user perspective. The use of user stories, help to create a simplified description of a requirement. Describing the type of user(s), what they want and why.
Card: User stories are traditionally written on note cards. Cards may be annotated with estimates, notes etc …
Conversation: Details behind the story come out during conversations with the product owner / client.
Confirmation: Acceptance tests confirm the story was coded and built correctly.
INVEST: Independent, Negotiable, Valuable, Estimatable, Small, Testable
With the encouragement and integration of User Stories in the Vocabulary Expansion Accelerator, our development processes have been efficiently directed to meeting the client requirements, producing tangible and testable functionality in conveniently calculated increments.
Stories are comprehensive (developers and clients understand them)
People are better able to remember events if they are organized into stories
Stories are the right size for planning
Supports and encourages iterative development
Can easily start with epics and disaggregate closer to development time.