For a project I am on we are looking to add more development resources and will be larger than what scrum recommends for a team size. As such the recommendation is to use a common product backlog and each team have their own sprint backlog. Would it be as simple as starting two sprints and then selecting which sprint when in the sprint board?
The best way to do this would be create a custom field of type Select list (Single) to separate Team 1 and Team 2, then while creating issue select which team the issue should be assigned by selecting the field.
Now to separate the Team 1 issue and Team 2 issue you have got the field.
Then create two boards with JQL saying
as [project = "" AND field = "" ORDER BY Rank ASC] for the board filter, where in field value changes.
This would track your sprints separate based on team in a same project.
Hope this helps !
Hi @Jerry Ward
Just to add to this, you don't need to create a new field for this. Many companies that I've worked with have used either the labels field or the components field to store whether an item is for Team1 or Team2.
You will also need to "mark" all existing items and any new items with Team1 or Team2, regardless of which field you decide to use
I agree @Warren
with last statement as it is obvious, the normal Jira user should know about this.
But the components is used totally for different purpose, to read more on this please follow the link https://confluence.atlassian.com/adminjiraserver/managing-components-938847187.html
And do you know why I specifically stated "Single" because in components multiple options are selected, same with the labels.
Many companies may use the components to differentiate teams, but as community members we should educate them about the uses of components.
Look forward to your reply and insights. Always happy to gain more knowledge.
And understanding the user requirement is must.
Everything I've read on Scrum states that the sprint backlog is for the one team, not shared. So the need is to have two different sprint backlogs. Further the teams may not have their sprints be the same length or stop/start on the same day. Before Next-Gen Jira I would just start two sprints from the same project. However in Next-Gen Jira you have to complete the active sprint before you can start another.
Next-gen Projects are made for small teams with different sets of goals...
Here is the link about Next-gen Projects.
https://confluence.atlassian.com/jirasoftwarecloud/working-with-next-gen-software-projects-945104895.html
There are so many limitations in Next-gen Projects for bigger teams.
The only reason we went with Next-Gen was for the road-mapping feature. Otherwise it is very limiting. If the road map feature would have been also released for original Jira we never would have switched.
It looks like you're new here. Sign in or register to get started.
