Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

What is the best way to manage a big list of projects for different customers?


Our work is divided into 2 parts:

1. Core product - managed by 2 teams which work with scrum methodology of 2 weeks iterations

2. Team that is dedicated to customers' implementation (independent from the core product and is not working agile. It has a separated project management life-cycle)

After reading different articles with different best practices I understand that the first part is pretty easy and the idea is to create 2 projects - one for each team (each team responsible for a different area in the product)

The second part is where I'm more confused - it looks like the right way would be to create a project for each customer (also, each customer has different branches which makes it more complex, as each brand has it's on project management life-cycle).

But moving forward as we grow the list of projects will get bigger and bigger - what are the pros and cons for a huge list of customers projects? is this the recommended approach? and what is the best way to manage a customer that has multiple branches and each branch should have it's own project life-cycle? (would component be a good solution?)


1 answer

0 votes
sukkeong Rising Star Feb 17, 2020

It appears you are facing Conway's Law,, which your system is mirroring your organisation.

My team admins a JIRA server with too many projects than needed. JIRA is still working fine and everyone adapts to the growing pains.

We periodically review if the current setup is fit-for-purpose. Changes to current setup often involve organisational and mindset (management approach) changes to be successful.

In the end, it probably depends on how your organisation works best.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events