Table of Contents
Creating Stories
Jira for Scrum Masters: Creating Stories
Creating Stories in Jira is the process of capturing user requirements in a simple, understandable format that describes a feature from the end user's perspective.
Key Idea:
User Stories help Agile teams understand what needs to be built, why it is valuable, and who will benefit from it.
User Stories help Agile teams understand what needs to be built, why it is valuable, and who will benefit from it.
What is a User Story?
A User Story is a short description of a feature written from the perspective of the user who will use the functionality. It focuses on business value rather than technical implementation.
Standard User Story Format
Format:
As a [User Type],
I want [Feature/Functionality],
So that [Business Benefit].
As a [User Type],
I want [Feature/Functionality],
So that [Business Benefit].
Example User Story
User Story:
As a customer,
I want to reset my password,
So that I can regain access to my account if I forget my password.
As a customer,
I want to reset my password,
So that I can regain access to my account if I forget my password.
Components of a User Story
| Component | Description |
|---|---|
| User Role | Who will use the feature |
| Requirement | What functionality is needed |
| Business Value | Why the feature is important |
| Acceptance Criteria | Conditions that define completion |
Acceptance Criteria Example
Password Reset Story:
- User can click "Forgot Password"
- System sends reset email
- User can create a new password
- New password meets security requirements
- User can login using new password
Steps to Create a Story in Jira
- Open Jira Project
- Click Create
- Select Issue Type as Story
- Enter Story Summary
- Add Description using User Story format
- Define Acceptance Criteria
- Link Story to the appropriate Epic
- Assign Story Points
- Save the Story
Story Hierarchy in Jira
Hierarchy:
Epic
├── Story 1
├── Story 2
├── Story 3
└── Story 4
Epic
├── Story 1
├── Story 2
├── Story 3
└── Story 4
INVEST Principle for Good User Stories
| Letter | Meaning |
|---|---|
| I | Independent |
| N | Negotiable |
| V | Valuable |
| E | Estimable |
| S | Small |
| T | Testable |
Role of Scrum Master in Story Creation
- Facilitate backlog refinement sessions
- Ensure stories are clear and actionable
- Verify acceptance criteria are defined
- Help split large stories into smaller stories
- Support Product Owner in backlog preparation
Best Practices
- Write stories from user perspective
- Focus on business value
- Keep stories small and manageable
- Define clear acceptance criteria
- Link stories to appropriate Epics
Common Mistakes
- Writing technical tasks as stories
- Missing business value
- Stories that are too large
- Unclear acceptance criteria
- Not linking stories to Epics
Example Interview Answer
Answer:
A User Story in Jira is a requirement written from the user's perspective that describes a desired feature and its business value. Stories help Agile teams understand customer needs and deliver incremental value during Sprints.
A User Story in Jira is a requirement written from the user's perspective that describes a desired feature and its business value. Stories help Agile teams understand customer needs and deliver incremental value during Sprints.
Conclusion
Creating effective User Stories is fundamental to Agile success. Well-written stories provide clarity, improve collaboration, and ensure the team delivers features that provide real value to users.
Scrum Master Complete Bootcamp: From Beginner to Professional