Structure of Epics and Project backlogs.

[Dan Evans]

Hi,

We're looking at our current process with JIRA and are looking at whether there is a sensible structure.

We're looking to create a project for the whole department where only Epics are created.

From that each team will have its own project/backlog where they can review the Epic and create user stories in their own backlog.  These user stories should be linked back to the central Epic from which it was based.

The central Project's Epics should be able to list all user stories from the many individual teams - so Epics can be tracked.

Conversely, we should be able to see which user stories in the individual teams have been linked to the epics in the central project.

Is this possible or even a sensible approach?

Thanks,

Dan.

[Jack Brickey]

@Dan Evans, I don't want to judge your approach TBH as I don't really have all the data that drove you to this. With that being said, I would likely look at this approach:

• Stick w/ one project (unless there is a reason to have multiple, e.g. your dealing w/ multiple products)
• leverage Components for each 'team' rather than projects as you mentioned
• each team can have their own board (kanban or scrum) w/ the filter excluding all components except theirs
• if desired have another combined board that includes all issue BUT avoid enabling ranking on that board so as not to override the ranking done by the individual groups/boards.

just off the top of my head something to consider.

[Dan Evans]

Thanks for your feedback @Jack Brickey.  I'll look into that approach and see where it takes me.