pros and cons of having two different teams work multiple sprints and issues from 1 project?

[GR VERNER]

We have a design team that is split into 2 teams that manage sprints from 8 other project work streams. I want to have a Design 1 project and a design 2 project letting both design teams work their own sprint and issues in their respected projects.

It has been suggested that we combine our projects into one project and run multiple sprints with different issues from all work streams for both teams in it. I think this would be Messy and a bit of a nightmare tagging issues associated to team 1 and team 2 then making multiple boards and so on.

Trying to figure out the pros and cons of working either way.

Any insights on why NOT or why we would even WANT to do this is appreciated :)

[Deleted user]

Hi @GR VERNER,

My points surrounding the comparison are below, neither are specifically pro or con as that is dependent on the configuration of Jira and the organisation using it;

2 Projects

• Use issue links where dependencies are present between teams.
• Sprint can be limited, as you mentioned, due to only 1 team working on a sprint.
• Teams are collaboratively silo'd, though they are both design teams.

1 Project

• Use Components on tickets to denote each team's responsibility.
• Sprints could be larger for both teams to sift through (quick filters helps here).
• Parallel sprints could be set up if both team follow different sprint timescales.
• Team collaboration is improved on work packages that need resources from both teams.
• You mentioned Sprints so I can assume you follow the Scrum framework. Scrum ceremonies such as Sprint Planning & Retrospectives will consume more time however there will be fewer events that block both teams from actual design work. 

Hope this helps

[GR VERNER]

Thank you Danny! It seems the separate Project approach would have better benefits as we do our own Retrospective after each 2 week sprint.

[Deleted user]

I’m glad I could help :)

thanks Gilbert