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

Next challenges

Recent achievements

Recognition

  • Give kudos
  • My kudos

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

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

Hello,

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?)

Thanks!

1 answer

It appears you are facing Conway's Law, https://en.wikipedia.org/wiki/Conway%27s_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
TAGS
Community showcase
Posted in Jira Core

How to manage many similar workflows?

I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...

3,971 views 11 5
Join discussion

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you