Home / BA / Epic v/s Themes v/s User stories

Epic v/s Themes v/s User stories

Once the project is kicked off BA gets the requirement and  he listed Requirement as FEATURE LIST .  From the Feature List BA identifies Epic and breaks them as Theme and then to User Stories .

 

 

EPIC – It is High level of Information . Epic is large user stories which if BA wants to implement ,  it must be 1st broken up into several smaller User stories .

THEME –  Epic further divided in Theme. Theme is little elaborate description of Epic . It is  group of related user stories where the stories usually do not have dependency on each other  .

USER STORIES – Theme further divided into user stories . It is a crystal clear complete form of a requirement .

 Syntax for user stories –       AS A < ROLE >

I WANT  < DESIRE / GOAL  >

SO THAT < BENIFIT >

Example –               AS A CUSTOMER

I WANT USER ID AND PASSWORD TO LOGIN

SO THAT I CAN PERFORM SOME ACTION

 

      Acceptance Criteria :- Every user stories must have acceptance Criteria . This area will have mandatory information that are needed in user stories .

Example  :     1) User should have valid ID and Password

2) User should get home screen .

 

Syntax for Acceptance Criteria –     GIVEN < SCENARIO >

WHEN < PRE CONDITION >

THEN < RESULT >

Example  –             GIVEN ACCESS TO LOGIN PAGE

WHEN HE ENTERS VALID USER ID/PASSWORD

THEN USER CAN ACCESS HIS / HER HOME SCREEN

 

About Jaishree Singh

Check Also

Acceptance Criteria, Business Value and Complexity Point in Scrum-

Acceptance Criteria: Acceptance Criteria are the conditions or stories that a software system product or …

Leave a Reply

Watch Dragon ball super