One "Project" or Many with bit bucket integration

When setting up our backlog what are the pro's and con's of multiple Projects in jira? We have bitbucket and Jenkins and we want to fully integrate the capability for tracibility and versioning. Our team of architects believes separate Projects by Products is cleanest but I'm concerned about having multiple Projects because often times when we release, we push out 2 to 3 Products into one release. I believe having 4 Projects (for our 4 products) requires the PO to write stories in different backlogs. Thoughts? 

1 comment

You will have to write different stories but doesn't it make sense because they are for different products?

And having stories in different projects doesn't mean they cannot go into the same backlog. You can have a single board for all those projects if it is the same scrum team that is working on it. Boards belong to the teams, not to the project.

There is no disadvantage in terms of the integration as well. In the end, it depends on your process because JIRA can handle both approaches.

Comment

Log in or Sign up to comment
Community showcase
Published Nov 06, 2018 in Bitbucket

Upgrade Best Practices

Hello! My name is Mark Askew and I am a Premier Support Engineer for products Bitbucket Server/Data Center, Fisheye & Crucible. Today, I want to bring the discussion that Jennifer, Matt, and ...

244 views 3 7
Read article

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