Can we have different methodologies and work on the same project?

[Eran Betzalel]

We have two teams in our company, Software Development Team and Algorithm Team, both use Scrum.

About 10% of our work is shared, meaning, working on the same issue. We created 2 boards under the same project.

The problem started when we realized that we have different ways to work, different workflow and statuses.

Also, we have to separate our issues in the Board filter by custom field named Team. Whenever we forget to set this custom field, the issues disappears and default value can't be set by the current Board - only by the current Project.

What would you suggest changing? should we work with separate projects or continue with the shared one?

[Petter Gonçalves]

Hello @Eran Betzalel

Thank you for reaching out.

I believe you can use one of the following approaches to properly manage both teams with their own scenarios:

1 - Keep both Software Development and Algorithm Team in the same project, however, using two different issue types.

Following the approach above, you will be able to configure two different workflows and default values for your custom fields (By using the workflow post function update issue field) to both teams.

The documentation below gives you instructions on how to configure a workflow scheme to your project, using different workflows for each issue type:

- Configuring workflow schemes 

In fact, you would not even need a custom field to differentiate both issues and create the boards since they are already using two different issue types.

2 - You can use two different projects to administer both teams. 

This approach is pretty intuitive, and also allow you to configure and engage both in the same issue when needed.

Also, this option will allow you to better restrict the permissions of each user, since you will have two different set of project permissions.

With the details you provided so far, I believe that both options should work for your scenario.

Let us know if you have any questions or if you see any details/requirements of your teams that are not being considered in the approaches above.

[Eran Betzalel]

What would be the disadvantages of separating to two projects? what won't I be able to do?

[Petter Gonçalves]

Hello @Eran Betzalel

I can not think of any disadvantages of separating your team issues in two different projects. Actually, this option will give you more ways to customize your permissions, as explained in my last reply.

Anyway, if you find any inconveniences when using one of the options above, you can easily change it posteriorly by using the Bulk Operation functionality and move your issues to a different project or put them together in the same project with a different issue type. 

Let us know if you have any other questions.