Best Practices to use "Atlassian Team"

[Patrice Champet]

Hello,

We are migrating to the cloud, and it appears that Atlassian Team could be very useful for us to manage and share information accross our teams.

But in order to manage it for the wole organization we need to ensure the consistency of the teams declared.

I mean it is good to be able to create teams for a specific need, such as a small project, it helps a lot to break silo.
But we fear that each Team create his own Team several times with no clear naming convention making it hard to search and use.
For instance having teams "IT - Network", "Network", "Organisation - Network" and so on... 

Do you have any best practices to share in order to keep the list of teams accurate with the organization ?

Thanks a lot.

[meinhard_schramm]

Hi Patrice,

have you found a solution for a naming convention for teams? We have been considering the following:

<level1> - <level2>

Functional / line management:

• Data - BI
• Data - ETL
• Data - DBA 
• etc

Project Perspective

• Project A - All
• Project A - Data
• Project A - UX
• etc

Additional views could be by product, special teams (e.g. ad hoc support).

Have you found a way to monitor / to manage the team names?

Regards,

Meinhard