Forums

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

Setting up Projects - Teams vs. Products

Jamie Stanczyk
Contributor
July 14, 2025

Good morning!

I wanted to get feedback on setting up projects within Jira. Currently, our Jira instance is setup to where each product within our company has its own project. This is helpful for us as we have multiple teams that work on one product, so we are staying product management focused. 

And this is where the discussion and advice is needed. We also have teams that work on multiple products, so tracking individual team velocity, burndowns can be difficult. Along with having products as projects, I also have project for each team, with a cross-project filter that shows all of the work that they are doing for their given sprint. However, viewing the project burndowns are difficult as those reports are based on sprints, not on teams. I have found multiple other posts with this dilemma, and it seems like an additional plug-in app maybe necessary.

So this question, is two-fold:

  • Is it best to keep our setup of product for each project, with our unique structure?
  • How is best to get team velocity/burndowns with this product management focus Jira setup?

1 answer

1 vote
Walter Buggenhout
Community Champion
July 14, 2025

Hi @Jamie Stanczyk,

I' d be happy to take your discussion into the agile group here on Community and see what advice might come out of there. It would be great if you could post your question as a discussion there and I'd be happy to try and get some traction around this topic there.

From my perspective: I don't immediately see the need for apps just to track burndowns. Sprints are a planning vehicle for teams, in my book. And I can think of other options to track work from a product angle, such as epic and version burndowns on that end.

Hope this helps and looking forward to discussing further!

Jamie Stanczyk
Contributor
July 14, 2025

Thank you. I did post it in the Agile group. 

And to give a bit more background, the sprint burndown reports would be for teams to understand their work within a given sprint. With some teams working on multiple products, they still need to understand how much work they are doing in one sprint, over multiple products.

Suggest an answer

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

Atlassian Community Events