Home / BA / EPIC v/s THEMES v/s USER STORIES: FEATURES LIST IN SCRUM

EPIC v/s THEMES v/s USER STORIES: FEATURES LIST IN SCRUM

To start with, Once a project is kicked off, BA dos the requirement Planning, then conducts various requirements gathering sessions and analyses the requirement. Finally the requirement is listed as “FEATURE LIST”. This feature list is drafted by BA and discussed with Product Owner. This feature list will have all enhancements and existing features (If it is migration project).

From the feature list, BA identifies the EPIC and breaks them as THEMES and then to USER STORIES

Epic Themes User stories
Epic resembles the themes in the senses that they are made up of multiple stories Themes are group of stories that are related. Smallest unit of work, also known as a task.

 

User Story:

A user story is a tool used in software development to capture a description of a software feature from end-user perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement.

User story will have below information:

As a

<user>

I want to

<What is the Purpose>

So that

<What you gain by this story>

Example:

As a

Customer

I want to

Login to the net banking site

So that

I can perform banking activities

 

Epic:

It is high level of information. It is large user stories which if BA want to implement , it must be first broken up into several smaller user stories.

THEME:

Epic further divided into theme. Theme is elaboration of Epic. A scrum theme is the highest level of the story hierarchy. It is group of related user stories where the stories usually do not have dependency on each other.

Acceptance Criteria:

This area will have mandatory information that are needed in the story.

About M.Sree Divya

Check Also

RISK ANALYSIS & MANAGEMENT

RISK ANALYSIS & MANAGEMENT Any uncertainty event (Flood, fire, rains) or condition(unavailable of resources or …

Leave a Reply

Watch Dragon ball super