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

How do you make Scrum under Waterfall? Very often the Scrum under Waterfall exist in organisations. It might not exist formally, but it can be required by contract or by law. The Scrum can be part of the Agile experiment. The Scrum under Waterfall be because it's practically for the or...
9 main Agile software development Methodologies Agile Modeling Set of concepts, principles and techniques (practices) that enables you to quickly and easily perform design and documentation for software development projects. Does not include detailed instructions on designing, contains descript...
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...
Waterfall vs. Scrum What is “Waterfall”? Waterfall is a plan-driven project management in software development. So normally you work with Gantt charts & Microsoft Project, you have Start & end dates and Project phases. In Waterfall, development phases have fo...