02-09-2018 04:25 PM
02-09-2018 04:25 PM
We are a medium size contractor. We have 30-50 customers, we complete 1-100 projects for each, per year for. They range in length from 1 day to 12 months.
Right now we hold each project in a channel, under the "projects" team. Everyone in the company has access to each project, but don't necessarily need to.
Problem is, by the end of the year the channels within the "projects" team, will be a mile long.
How should we set up Teams?
All advice is welcome!
02-09-2018 06:53 PM
02-10-2018 12:11 AM
02-10-2018 02:30 AM
02-10-2018 04:15 AM
OK, so set up each team as a customer and project for that customer as channels? Then use Project online for control of said project?
02-10-2018 04:21 AM
02-10-2018 12:35 PM
Think of a team as a boundary, if you need a different list of users to have access to a set of conversations and files then create a Team.
Teams can handle lots of Teams and lots of channels in each Team, it'll only show you the things you favourite in the left column, those which arent favourited get put under 'more' links. For example I'm in about 30 Teams but only favourite 4 o fthen to keep an eye on, and then I pick the channels I need.
I couldnt really say in your case, perhaps managing permissions on having lots of teams would be a pain when someone new joins, in which case I might stick with the 'projects' team you discuss. Or perhaps grouping customers allows a better understanding and you can see more at a glance which projects are noisey etc.
02-18-2018 08:43 PM
05-26-2018 03:34 AM
Watch out for the limit on the number of teams and channels currently. I'm looking into using teams for our project work in my department but there is a 200 channel limit per team which is less than half a years worth of projects for just our small team. I understand there's a workaround of deleting the channel while the data would remain on the sharepoint site but I'd like to retain easy access to older projects for all the users who don't necessarily have any sharepoint knowledge. I think there's also a limit of 250 teams so I couldn't make a team per project either. I'm not sure if Microsoft don't intend this to be used for all projects over many years or if this will get fixed but at the moment it's something I'm concerned about.
06-19-2020 06:54 AM
I'm a couple years late, but was curious if anyone that commented had any updates.
In my view, it seems that a Team would be a project and the Channels would be the topics that pertain to the project. This way, you could probably standardize on Channel naming-conventions to a large degree and get users used to what content applies to what channel - e.g. a "Submittals" channel and an "RFI" channel - things that are common to all projects.
Also, you might have a single client, but different studio in your firm manage different projects for that client - in that scenario having one Team for the client could get messy with lots of users working on different projects. Or maybe not. ¯\_(ツ)_/¯
I would love to see an example from Microsoft where they map out in a huge diagram how they envision all these products being used.