Creating Epics for Scrum Project

How do I decide what will be an epic in my Scrum project? Say, for example, I create - Frontend and Backend as two Epics in my project, these two epics is never going to complete as we will definitely have new tasks related to it every week.

I went through many discussions related to Epics in JIRA, but could not get a solution for the same.

Please help!

1 answer

1 vote
Tarun Sapra Community Champion Aug 22, 2017

Hello Archana,

Yours is more of a functional question than tools based.

Here's how I would implement it.

Stories are generally sprint specific (2 weeks of work at max). Epic are genenrally release specific (upto 2 months of work) . Make sure you split your work such that you have Epics which are time-bound and also you can have open Epics.

For example - Create REST APi for exposing backend functionality. This can be an Epic. Now once you complete the work (in approx 2 month) then this Epic can be closed. 

 

Going forward , you can havea  component called "back-end API" and any new changes ("small stories or bugs) that are created will use that component. So that you can track which stories and bugs belong to the components.

For every release you can have something called "Spike" Epic, which represents such stories or bugs which are imporvement/bugs on already closed epics but having right component (like API) for better classification of work.

 

Hoping this helps.

Hi Tarun,

Appreciate your prompt reply. 

Now when you say epics are release specific, i think creating versions would also help us categorize tasks/issues. As per my understanding, a version can have multiple epics just like how epics can have user stories that span over multiple sprints. 

How would you suggest grouping epics then?

Epics can be grouped under initiatives (If you have JIRA portfolio add-on installed) And you can add fixe/version to Epics and each release (version) can have multiple epics.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,282 views 14 20
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot