• Community
  • Products
  • Jira
  • Questions
  • How do I setup JIRA for the Large Scaled Scrum Framework (LeSS)? It means one Product backlog for more teams (3 Sprint backlogs).

How do I setup JIRA for the Large Scaled Scrum Framework (LeSS)? It means one Product backlog for more teams (3 Sprint backlogs).

Hi All,

please could you help me with complexity problem in JIRA regarding managing one common product backlog for more teams (3 Sprints backlog). Distribution user stories from one product backlog to 3 sprint backlogs (3 countries with different responsibilities for development particular system).

Many thanks, James

 

 

4 answers

1 accepted

Accepted Answer
0 votes
Gaston Valente Community Champion Mar 14, 2017

Hi Jakub,

At Applications > JIRA Software you can configure parellel sprints:

Screen Shot 2017-03-14 at 09.33.30.png

 

Then you can setup three separete boards, each one based on a filter based on a field that indicates the country and share it with the team members.

Is this what you're looking for?

 

 

 

 

Hi Gaston,

Many thanks for your advice! Yes, it is exactly what I am looking for. Based on your very beneficial recommendation I setup JIRA (result please find attached below), make sense this way from your perspective? I am still looking for better tagging/labeling stories (than re-use Versions, Epics for different purpose) and also mainly way of evaluation sprints between sprints (I am not sure that Velocity chart will work for every Sprint backlog).

Do you know this Portfolio Add-on (https://www.atlassian.com/software/jira/portfolio) or please do you have any other ideal how to manage this?

Many thanks,
Jakub

image2017-3-14 18:56:52.png

 

Gaston Valente Community Champion Mar 15, 2017

Jakub, how are you labeling stories right now? and how do yo manage sprints between sprints?.

Have you dug into the Swimlanes yet? Swimlanes allow users to use one board for multiple projects such as backlogs. Is this what you are looking for? If so, I can explain more

Hi Thomas, thank you, probably I am looking for little bit different approach as Gaston wrote below. I will be glad if you have any other recommandation for this approach parallel sprints. Thanks, Jakub 

Our teams set up is a little different. We have several products and all teams can work on any product's stories/features (whatever is the higher priority for the company at the moment), this is in accordance to LeSS. 

Because of this, the filters for our teams' boards all import tickets from multiple projects (JQL is something like project = X OR project = Y ... etc). Each project has a different PO that has set up their projects using the specific workflows for their products. Some of these workflows have different Definition of Done, and other differences. 

The problem arises, when one team's board needs to show tickets from different projects on the same sprint. If you set up the columns for one project's workflow (associating columns to statuses), you might be messing up the association for the other project, since they have different workflows.

Has anyone else encountered this problem? 

Suggest an answer

Log in or Sign up to answer
Community showcase
Posted Sep 18, 2018 in Jira

What modern development practices are at the heart of how your team delivers software?

Hey Community mates! Claire here from the Software Product Marketing team. We all know software development changes rapidly, and it's often tough to keep up. But from our research, we've found the h...

23,760 views 2 7
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you