Forum Discussion
Implementing Teams
Hi,
We are looking to implement Microsoft Teams across our organisation.
We are interested in talking to anyone who’s rolled out Teams (successfully or not) to find out what you did, as well as what worked and what didn’t.
We’re particularly interested in the approach taken to training and comms, as well as the activities needed to set-up Teams properly for widespread usage.
All contributions would be gratefully received - thank you!
- Bola -
2 Replies
- AshishKamotraCopper Contributor
Rolling out and Adoption are two separate challenges when it comes to MS Teams or Office365 in general. Leveraging existing functionality is important for business users to take advantage of Teams. Once Teams is rolled out in your company, next step would be to bring Document management, Intranet, project management, knowledgebase within Teams. That way your employees will find all the relevant information within Teams.
We have done this and I can showcase that to you for your understanding and future planning. Building a roadmap is very important for Office365 and Teams rollout. Teams is lot more capable that what it seems. You can contact me if you want to see how we are using Teams with extended functionality.
Ashish Kamotra
a.kamotra@adapt-india.com
- Andrew HodgesBronze Contributor
Hi bodumosu ;
Setting up Teams- when creating multiple teams we created PowerShell scripts that provisioned a template as well as adding the users to the Team. This cut down on the time to deploy the teams. Tabs were pre-set so that the Team wasn't empty and linked into the Intranet and external website for instance. This tied the wider digital workplace into Teams.
Adoption - that many users will need some well thought through adoption strategy but we like to have all training material in one place in SharePoint and provision that as a Tab in each team. As training 15,000 users/students is probably out then some targeted online training for the Team owners covering governance, do's and don't, polices and procedures is probably a good idea.
Governance - what users can and cannot do in a team will be important, i.e. you may only want owners of the team to create channels but OOTB all members can. Guest access will likely be on as it is a blanket org wide setting so Owners will be able to invite external users so it is important that Owners are trained in Data security
Document Management - thinking about how you tie in existing SharePoint sites or using the SharePoint sites that are provisioned with the Teams.
Hope that helps.
Andy