User Story Scenarios

Each User Story needs to be testable, need to demonstrate, that requirement has been met. Here is effective formula, which demonstrate, that specific user story has been met:

Given <context> [and <more context>], When <something happens> Then <outcome> [and <another outcome>]

Here is the example of using this Given/When/Then recipe, which specify furfure detail, about the original user story. Before it was broken in smaller user stories und now it is associated to Given/When/Then Criteria.

Title: User cancels reservation

User Story:

As a user with a reservation, I want to cancel my reservation so that I get a refund.

Scenarios of user story:

Scenario 1: User is a premium member
Given
I am a premium member, when I cancel under 24 hours, then I incur no penalty.

Scenario 2: User is a typical member
Given I am a non-premium member, when I cancel less that 24 hours in advance, then I pay 50% fee.

Scenario 3: Email confirmation
Given I am a site member, when I cancel my reservation, then I am emailed a confirmation.
Very offen Team puts the whole user story on a card, which calls Story Card.

User Story Card

user-story-card
Here you can find user story title, description or user story and success criteria or scenarios. At the bottom of the card we can also see the estimation information for the card.

Related Post

Integration Team in Multi-team Scrum If one team in Scrum not enough, it's advisable use Multi Team. But here you get one more problem - how to manage more than one team. And the answer: use the Integration team. With Multi Team your Scrum will look a little bit different. Multi-team...
User Stories User Stories are an Agile term for what traditionally have been called "software requirements". They are a brief statements of the intent or need that the system must do for a particular users. Here is the basic formula of writing a user story: A...
Understanding Product Owner Role Responsibility Must have a Shared Vision Developing Winning product Product Owner controls the development effort in order to create a product Other Features A) Create Product Vision B) Maintaining the product backlog C) Release pla...
3 Levels of requirements in Agile development In Software Development Requirements have 3 levels: - expanded description of customers business - business point of view requirements - functionalities which should be made in our application Example: “We need a tool for selecting big data...