Forum Discussion
Establishing Teams Structure
Hi everybody. We need to establish a more rational way to set up file storage and directories in Teams. It is too random as it is. Thanks.
Karuana_Gatimu_MSFT
Community Manager
Community ManagerHI there. I have a video on this topic that is still relevant you may want to review. I'd also suggest using some of our built in templates and seeing how we've structured them. I took that content from research we'd done across many different types of organizations though nothing is ever perfect. They are designed to help people make their own and more tools for managing organization wide template store are coming. Meanwhile though I always suggest bringing people together to have the working team who will actually use the team, participate in defining it based on your own best practices. Here's the link to the video from my Coffee in the Cloud channel: https://youtu.be/WkAVgNKn0hs
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!