Features and User stories
Feature vs User Story
Feature: �Placing an order you have in your basket.
User Story #1:
AS A customer,
I WANT to be able to pay my order with different payment methods,
SO THAT it gives me a better flexibility to pay.
User Story #2:
AS A customer,
I WANT the ability to input my address & contact details,
SO THAT the order can be delivered successfully.
A feature is something your product has, such as functionality that enables users to do something.
A user story is a small chunk of work that delivers value, and can be completed within a sprint.
Think of user stories as a planning, and tracking tool.
Recap
What is a feature?
Features are large bodies of work that can be broken down into a number of smaller tasks (called stories).��What is a user story?
User Stories are short requirements or requests written from the perspective of an end user.
What is a task?
Tasks are a further breakdown of an user story, they reflect the hands-on work needed to deliver a story.
User Stories
A user story will describe the requirement at the highest level for a single feature with a regularized format: "As a (stakeholder) I want to (task) so that (desired result)"
Step 1: Think of the “Who”. Who the end users of your product are.
Step 2: Think of the “What”. What functionality each user expects, how he’s going to interact with the app.
Step 3: Think of the “Why”. Value that users get after performing an action.
Step 4: Discuss the story with your team, even if it seems like nothing to talk about. We ask the author of the story to provide more details or clarify something if needed. It helps us understand how it should work.
Recap - User Stories
Persona
- Who is the end user?
User stories are the end-user’s desires for the product
<As a [role], I want [objective], So [benefit]>
Value
- How does this benefit the persona?