User Stories - DavidMyrseth/BuketovPY GitHub Wiki

User Stories — User-Focused Requirements in Agile

Introduction

User Stories are a simple and powerful tool in Agile software development that describe functionality requirements from the end user's perspective. Stories help identify what the user needs and why, without unnecessary technical detail.

Definition

User Story = A short user-centered requirement

It follows a simple template:As a [type of user], I want [goal], so that [value/result]

Example:As a customer, I want to add a product to favorites so I can return to it later.

Structure of a User Story

Role: Who is the user? (e.g., administrator, customer, guest)

Action: What does the user want to do?

Value: Why does the user want it? What outcome are they looking for?

Optional additions to a story:

Acceptance Criteria: Conditions under which the story is considered complete

Priority: Importance of the story

Estimation: Approximate complexity or effort required

Benefits of User Stories

Focused on user value

Easy to understand for all team members

Encourage communication between stakeholders and the team

Integrate well with Scrum, XP, and other Agile methods

Help with prioritization and requirement breakdown

Example Story

As a registered user, I want to view my order history, so that I can track past purchases and reorder if needed.

Acceptance Criteria:

Order history is visible after login

Each order shows date, amount, and status

User can reorder with one click

Working with User Stories

Creation — collaboratively with stakeholders and the team

Discussion — clarify details and ask questions

Estimation — assess complexity (e.g., using Planning Poker)

Development and Testing — implement based on acceptance criteria

Demo and Feedback — present results and adjust if needed

INVEST Principle for Good Stories

A User Story should be:

I — Independent

N — Negotiable

V — Valuable

E — Estimable

S — Small

T — Testable

Common Mistakes

Story focuses on technical details instead of user needs

Stories are too large or vague

Missing acceptance criteria

Stories created without user or business input

Useful Resources

User Story Mapping — Jeff Patton

Agile Estimating and Planning — Mike Cohn

Scrum.org: https://www.scrum.org/resources/what-is-user-story