What is a 'User Story'

User Story 
- A user story is a description of a requirement from a user's point of view.
- Requirements are captured on a piece of card, 3 by 5 inches in dimension.
-Each User Story should fullfil The INVEST Principle:
Independent
Each uses story should be self-contained from all the other user stories in the product backlog.
Why
That to avoid getting the project in a situation where you cann't start a user story owing to the fact that this story have a dependency on another story.
Negotiable
Negotiable means that all the team members with different roles, are able, at all times, to negotiate what is on a user story by having a discussion with the product owner.
Why
To make sure that the right decision is made, on all dimensions (Technical, Bussiness, Testing, Data...etc).
Valuable
Valuable means to make sure that any user story actually really has a value.
Why
To make sure that nothing is done unless it's really going to give a return on investment or a specific value to the business, because there's no need to be doing any work unless it actually pays the business back.
Estimable
Every user story should be written in such a way that a team can read it, understand it, and put an estimate against it.
Why
That to avert getting the project in a situation where you cann't start a user story owing to the fact that this story have a dependency on another story.
Small
This means that you can deliver small pieces of value throughout the lifetime of the project.
Why
To ensure that any large problems must be broken down into smaller ones before they're written on what we call a user story.
To ensure that a product owner can be satisfied that they will get something that they can take to market as quickly as possible. 

Testable
One of the key principles within Agile, and in particular within Scrum, is a concept of a piece of functionality being done. And usually a piece of functionality is not done, or a feature is not done, unless it is tested and a tester has verified that the feature meets the quality standards.
Why
To make sure that anything that is delivered by an Agile Team has a high standard of quality to it. And that's it.






Paul VII. Agile Product Management: User Stories:  How to capture, and manage requirements for Agile Product Management and Business Analysis with Scrum (scrum, ... development, agile software development) (p. 22, p. 23, p.24, p.25, p. 26,p. 29). Pashun Consulting Ltd.. Kindle Edition. 

Comments

Popular posts from this blog

Maxpooling vs minpooling vs average pooling

Percentiles, Deciles, and Quartiles

Momentum