Forum Discussion
Establishing Teams Structure
Karuana_Gatimu_MSFT I have watched the video, very informative indeed.
One question to everyone though: we are a company that delivers (IT) projects to many clients, and sometimes different projects for different lines-of-business for the same client.
From people's experience, what are the pros and cons of having
- a Team per client, with projects as channels vs
- a Team per project, with channels for releases/domains (or what else?)
I'm looking for matters of practicality, visibility, app availability etc etc that you only realize after you've done it for a while... Thanks!
One of the most important points would be to think of how often you will be doing a project with each client. If you're going to be doing several projects with a single client, it's easier to house all projects in one Team (M365 Group) /SharePoint/email.
Example:
Team = Contoso Project Managers
All projects, documents, power bi dashboards, etc is housed in one Team and SharePoint site (M365 Group) .
Any team member that is added to, gets access to all of the above in the past and going forward.
On the flip side, if you're going to want different permissions per project, it may be better to make individual Teams (M365 Groups) for each project.