I work within a large Marketing department consisting of 19 teams. We have found that the best way to set-up Jira (Server) is with one project and a custom team field to filter out work for each team. We have also created separate Scrum of Scrum boards for large project based work that multiple teams contribute to.
At the moment I am trying to figure out whether to allow each of the 19 teams to start/stop/edit their own sprints or if this should be managed by one admin team.
Currently an admin team is managing this and I wondered if anyone had any experience experimenting with these options and what conclusions or considerations they found?:
Thank you so much!
Hello @Amy Likoravec ,
We have a project with 7 teams.
We created 7 Boards, And For each time we created a component.
Whenever an issue is created, that must be tagged with the component name. and each scrum board is configured with a filter representing each and every component.
on sprint main board , If you want to create a sprint with all issues from 7 teams you can enable a single user / Project admin to manage sprint.
If you want create separate sprints for each and every team, You can create a separate role as "Team Lead" and add only users who are able to perform Sprint Start / Sprint Closse operations. And add the "Team Lead" to sprint manage permissions.
Try the one which suits your need.
Thank you for your response, however, I am specifically looking for a bit more detail about what the impacts are for both options.
I'd prefer not to make any changes until I know that nothing will break or be affected from making this change (i.e. allowing teams to manage it themselves instead of a central admin team).
So far the considerations I have found are below, however, I don't think I have considered everything or if the considerations are even correct:
ADMIN MANAGES SPRINT START/STOP/EDIT
TEAMS MANAGE OWN SPRINT START/STOP/EDIT