Best way for separate engineering teams to work together and seperately

[Ben Weisman]

Hello,

   I have 8 engineering teams using Scrum. Much of their work is shared within epics so we have created a combined scrum board for collaboration. With that said, some of their work is silo'd and autonomous. What's the most efficient way to accomplish this with sprints/boards?

Thanks.

[Mark Segall]

Hi @Ben Weisman - I have found it best to keep it simple on the individual teams.  Give them a project-specific board that they work within while program leaders use the consolidated board for their needs.  This way each team gets the personalization of setting up individual quick filters, swimlanes, card colors, etc. that work for them and the program team gets the view they need.  The most important thing is to ensure that the engine behind it all (workflow) is as close to consistent as possible so that you're not having to compromise on reporting needs.

[Ben Weisman]

Thanks @Mark Segall . In the way you're doing it, how would sprints be handled?

[Mark Segall]

You can still create your sprints on the consolidated board.  Though, the sprints won't show on the individual boards until you've dragged at least one issue into them from the consolidated board.

[Ben Weisman]

So you'd suggest having the teams keep separate sprints even though they're working on the same Epics?

[Ben Weisman]

@Mark Segall 

[Mark Segall]

I think it depends upon your structure.  If all teams follow a consistent cadence, where sprints start/end on the same day, there's no harm in sharing a sprint across projects.