How can I make 3 teams utilise the same epics

[Scott MacKenzie]

I currently have 3 projects for the 3 teams that are building our product. 1x Fontend, 1x Backend and 1x Devops.

I'd like to get the 3 projects using the same epics. What is the best way to manage this:

1. Continue with the 3 projects and associate the issue type schemes as per the attachment?

2. Move the 3 boards to the 1 single project and filter the boards accordingly?

My end goal would be to create an epic board to manage epics and an initiative board to manage high-level business problems. Once that is established I'd like to get Portfolio running across the business. So it's important that the configuration is scalable to that future state.

[Lennart]

@Scott MacKenzie i'd go for seeing Initiatives as your 'shared epics'. There are probably many examples for structures out there. To give you an idea:

• Investment Area
• Initiative
• Epic
• User Story
• Subtask

Using ScriptRunner, you can display the upper levels on the levels below, i.e. Investment Area, Initiative on Epic /  Initiative and Epic on User Story.

I'd do it like this. I've understood your main target is a structure you can work on with your teams and your business. On top, you want the workers to have shared topics to work on, they should know about each other and integrate. This can totally be solved using the approach i've outlined.

Questions? Ask! :)

[Scott MacKenzie]

That is a good point and I have worked this way before. What are the cons of sharing Epics as opposed to sharing initiatives?

Really my goal for sharing epics across teams is reducing workload and given we are operating relatively in parallel across the 3 teams it just makes sense in my mind.