Inquiry about adding a new project

[blal jirjawi]

Hi 

I'm new in jira
I have been working on Trello

Now I have a large product that consists of several projects, and I want to divide this product
Do I work for each part of its own project? Like what is in the picture?

In the end, it is one product, but it is divided into projects
Is this correct ?

[Nic Brough -Adaptavist-]

Welcome to the Atlassian Community!

We can't tell you how best to break up your work, we can't know enough about the way you want to work without a detailed examination of what you are doing and how you want to be working.

However, we can give some advice:

• How do you want to be working?  Don't set up Jira to work the way you work now and then try to change it as your processes change, just set it up aligned to the way you would like to work. 
• Think of projects as issue containers, not real-life projects (although that is a perfectly valid thing to align a Jira project to).  The main thing about a Jira project is that it holds all the configuration - how each issue type works (primarily the fields it has and the workflow it follows during its process lifecycle), who can do what in the project, who gets emails about stuff, and so on.
• Align a project to something you can clearly define.  A team (alignment to a team works well if you have support projects, or isolated development teams that don't really work with others), a product, components of a product, a real-life project, or any other purpose.  (When we were smaller, we had projects for time off, sales, client projects, event planning, and and and)

The most important part of defining a project is thinking through how you want your issues to work in the same way and how people get to use them.  Focus on grouping issues into projects based on who will be using them.

Once you have your projects defined, move on to the boards.  A board is best thought of as "a team's place to track their work".  Most boards are simple 1:1 mappings with projects, but when you define projects that could need different teams working on them, you can, and should, create boards that show a team's work across many projects.

[Kelly Arrey]

Hi @blal jirjawi We have two major products, with several small teams on each product. We've chosen to have one company-managed project for each product. Each team gets their own board. We created a custom single-select field we call "Agile Team", which makes it very easy to filter issues in each project to the board for that team (We ran into a lot of issues when we tried to use the built-in Atlassian-supplied Team field). This setup works very well for us.

Separate projects for each team could also work, although it would be good to share workflows and issue type schemes and layouts across all teams on the same product if you went with separate projects. If each team has their own workflow, it makes it harder to see the big picture - each board has different columns, etc.

[blal jirjawi]

Hi, I am glad to hear that, but I have a big project and I want to divide it into parts, how can I do that? If only one project was done ? 

I'm new to Jira and I want the right way to do it

[Kelly Arrey]

How big is big? How many people are working on the project? There is no one "right way" to do a "big" project.

If you chose to use a single project, there are ways of dividing up the work . One way is to define a custom single select field like "Agile Team" so that you can specify on each ticket which team will be working on it, and use that to create filters for each team that they can use to define the set of issues that will appear on their boards. Or you could use an existing field like "component", although this drawbacks, because some tickets can be associated with more than one component, so the mapping of components to teams can cause some issues to appear on two boards and things like that. A custom single-select field avoids this problem.

If you want to have multiple Jira projects, that's not wrong. If you maintain common issue types, workflows and layouts across projects, that's only a little more work than administering a single project. The complexity of administering multiple projects increases as the different projects adopt different issue types, workflows, and or layouts. It may also make it more complicated to move issues between teams if that's ever necessary.  

As an aside, I have quite a bit of experience with company-managed Jira projects, and only limited experience with team-managed Jira projects. But from the questions and answers I've seen in the community, I'd recommend you choose a company-managed Jira project for your situation - they seem to be more flexible. Team-managed projects seem to have a lot of limitations and "gotchas".

This isn't the kind of question that has a short, simple, one-size-fits-all answer. Some experimentation will help you to learn how the system works, and what kind of set-up will be most effective for your team.