Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Suggestions on whether to use single or multiple projects for various parallel workstreams

Edmond Victor July 29, 2021

Good day,

Our company is running Cloud Standard version of Jira software so we only have an Issue hierarchy of Epic and lower. We also only have Roadmaps and not Advanced Roadmaps. We use Classic project and not Next-Gen.

As a BI Team we have recently decided to create dedicated workstreams to service different business areas in the company with Reporting, Analytics and DataScience products.

Continuous development

We have a dedicated team looking after Supply Chain another team looking after Marketing etc. The teams will remain mostly static and we will have a single backlog per stream of work. 

CAPEX Projects

Resources from the continuous development teams above could be moved onto pure projects as and when required.

The way I currently configured our environment is to have a single project per workstream (one active sprint and one used as a backlog). That way the team and workflow is the same for all work streams. I have two concerns with this approach. 1) 9 workstreams x 3 sprints (backlog, active, next) each becomes very messy in a single project. 2) Since we only have Jira Standard I am very limited to see a future view of work in the following iterations in a timeline view 3) We use EPICS to distinguish between the stories for each workstream but the roadmap view is very limited to show Stories and Sub-tasks.

Should I rather:

1) Use a different project for each workstream or

2) Upgrade to Cloud Premium

3) or how do I get better visibility of future sprints on a timeline view

 

Thank you

1 answer

0 votes
Yuri Lapin _Release Management_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 29, 2021

Hi @Edmond Victor

Trust you are well.

I bet one project is not scalable long term. You will also limit flexibility of workstreams manage their work and deliveries in slightly different way which is inevitable. That was practically the philosophy behind next gen projects. So, my take is "different projects".

But saying this you also need to understand the drawbacks. Yes, you will give workstreams the flexibility, same time you will be asked to consolidate reporting and provide abilities to manage work & dependencies cross-workstreams. The solution here is either Premium or start picking up Apps from Marketplace to help you consolidate and manage things cross projects.

We develop one of such Apps to manage deliveries cross projects and create release centric roadmaps. You might wanna try it out or request a quick demo here:

https://docs.google.com/forms/d/e/1FAIpQLSdvVBm5KK5wTNosLqyP9iKUI8GOoqZn8kQEyV-1yAOJZEwKxQ/viewform 

Cheers,

Yuri.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events