We have a project with 170 epics, and we would like to group them around specific themes in such a way that our product owners can reschuffle the priorities of these themes and the priorities of the epics within a theme.

Is there a way to setup a project / rapid board such that

a) A product owner can reprioritize on theme and epic level in the product backlog

b) When the team lead works on planning the sprint, the stories are prioritized according to the epic priority. For instance when epic 1 has a higher priority then epic 2, all stories of epic 1 have a higher priority than the stories of epic 2

What is the best approach ?

6 answers

1 accepted

The answer to this question is the structure plugin using a filter and a greenhopper synchroniser.

I just got of the phone with Igor from almworks.
We worked out a functional configuration in less than 15 minutes.
Great add-on - and great support.

An important note for anyone using Filter sync and GreenHopper sync altogether: always have GH sync disabled when resyncing Filter sync! If you need to recreate a Filter sync, this is the correct sequence:

  1. Disable GH Sync
  2. Recreate/resync Filter sync
  3. Resync and Enable GH Sync (direction: from GH to Structure)

Otherwise if you resync filter synchronizer with GH synchronizer running, it may change Rank/Epics in response to issues being added/removed at the top level.

Epics cannot be ranked/prioritized, that's a quality of single Issues only.

May I ask how did you end up with 170 Epics? It sounds like an excessive number for one Project. How fine-grained is your use of tasks, are you using Stories and Sub-tasks as well?

it's a large product with a lot of features, and a lot of people working on it. We do use stories and subtasks

I think there are a few ways you can group Epics into similar-themed groups:

1. Setup Versions for your project. These will appear on your Rapid Board. Assign Epics to Versions. This will allow you to group and view Epics that belong to a particular version. You can prioritize versions by assigning start and end dates. You will still not be able to prioritize all stories of an epic together.

2. Use labels to identify similar Epics. This will however not be visble on the rapid board and also not let you prioritize all stories from that Epic at once.

3. Revisit, from an agile perspective, how you define an Epic. An Epic is usually something that cannot be completed in a single go or a single sprint. An Epic is usually broken down into stories that can be completed in a single go. The stories then have tasks that your team performs to make the acceptance criteria happen. Here's a far-fetched example:

Project: Conquer Planet Mars

Epic: Build a Mars Lander

Story: Develop Landing Gear

The Mars lander, weighing 5000lbs, will be traveling at a constant speed of 300m/s upon impact with the Martian surface.

Acceptance Criteria: Landing gear should allow a Mars Lander to land successfully and not suffer any damage. Landing gear can be one-time use only.

Sub-task1: Investigate material requirements

Sub-task2: Build Lego Prototype

Sub-task3: Build real landing gear

Sub-task4: Test

In some cases, even this story can be broken down further.

Hope this helps. Cheers!

Epics of Epics pretty please or some other functionality - themes.  We have over 300 people potentially working on large features that go into our products.   But I see this as an issue even when we have 2 teams working thru multiple Epics.  There is no way to prioritize Epics, there no visibility without lots of funky queries to see if you are burning down thru the epics.  I realize most people use labels as 'themes', but other than arbitrary ways to formulate labels (add the quarter you want the epics to go out in, etc) there is no way to prioritize/rank.

Hi Doug, Our Structure plugin can really help with managing large Agile projects, some ideas here - http://almworks.com/blog/2013-12-managing-jira-agile-projects-structure.html How would you like to prioritize Epics?

Use our plugin Agile Board Filter and you'll be able to create filters around epics

panels.png

 

 

access.png

The Structure plugin is much more we need. We just want to be free to group Epics and/or Stories in Epics to see it in the left bar of the backlog an in reports of agile projects. An optional & additional status 'Mark as Ready (to be planned)' like 'Mark as Done' would help to get the left bar of the backlog and the reports (c)lean ;).

I have created an Epic in Project X, and created 6 tasks in that Epic. Then I moved the tasks - one by one - to Project Y, while modifying their task type to Epic.

I went back to the Epic in Project X, it had 6 issues, all of them Epics.

Yikes!

How did this work out for you? I'm looking for a similar solution. Did your workaround get the job done?

Suggest an answer

Log in or Join to answer
Community showcase
Teodora [Botron]
Published Feb 15, 2018 in Marketplace Apps

Jira Inferno: The Nine Circles of Jira Administration Hell

If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...

1,033 views 6 18
Read article

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