05Jun2018

How To Write Awesome User Stories?

Independent: It can be implemented in any sequence based on prioritization and arrangement of other user stories. It can be moved up or down the backlog, yet, it can be developed as it’s shippable on its own.
Negotiable: Product Owners should avoid adding detailed information in the body of the user story. This type of information can be modified until meeting customer expectation. Therefore, it should be mentioned in the acceptance criteria.
Valuable: What is the business value behind developing this user story? There should be an answer to the question or else there is no point from it.
Estimable: The team should be able to judge if the user story is small/medium/large or extra-large as they will use it planning the backlog then later when breaking down the tasks in sprint planning.
Small: The smaller the user story, the more focus it will get from the team. It would be easier to estimate, break it down to tasks and deliver it.
Testable: Providing the conditions that could identify how the story should be tested is crucial for a story to be done; and that is what we defined above in the acceptance criteria.

Overview In Software engineering, requirements gathering has multiple techniques. User stories are one of the most popular techniques in agile development. It’s a way to document stakeholders’ requirements in an informal manner. The primary focus of a user story, is...

Scroll

Analytics & Data Management

Digital Business Automation

Connectivity & System Integration

Enterprise Content Management

Enterprise Portal & Mobility