I am currently handling an MS365 rollout for my organization which has more than 100 users. I am new to the project. I need any information to help me carry out this project. If anyone can provide me with step by step procedure to complete this project. I will appreciate it if I can get a template. Thanks Saving Changes...
Sort By:
John DuncanRetired| RetiredLebanon, Tn, United States
Hi William. There can be a lot of moving parts to this. I don't think there's one template to fit all.
What's the scope? (Office 365, Outlook in the cloud, Microsoft Teams, Sharepoint, OneDrive)
What's the expected timing?
Who in I.T. is involved and what is their knowledge/skillset?
When we rolled out, we had a lot of in-house expertise and support.
What level of licensing are you looking at?
E1, E3, E5
Open License, Open Value Subscription, Open Value,
Open Value Subscription for Education Services
Do you need Visio? Project? SQL Server?
Are you leveraging, or can you leverage, Microsoft for guidance?
Some of the answers to your question depend on where you're starting from. For example, if you're currently using an older version of SharePoint, you'll need to figure out whether you can go fully in the cloud and determine your data migration strategy.
If you're currently using older versions of the desktop apps, it's not as complicated, but still not simple. Some people will only need the online versions of the apps; others will need a desktop versions. If your end user's computers are locked down so that only admins can install new software, you'll need to push a package with the right permissions or manually have an admin go to each computer (not ideal, but manageable for a smaller organization). If you have users who use VBA in Excel, you're going to want to make sure they test that their macros and code work in the new version, keeping in mind that the desktop version may do more than the online version.
Sorry for the disorganized brain dump. It's been over three years since I managed the rollout at a previous employer. I can't overemphasize the need for communication and change management on this type of change - it's almost more important than the technical aspects of the change. It might seem simple, but it can be disruptive to the end users. If you're current state is not Microsoft Office, you might want to plan for more resistance than if you were already using Microsoft tools.
Wherever you can, use the new tools to communicate the change. My sponsor sent out a weekly email, using the embedded video creation capabilities in PowerPoint, to highlight new and interesting features. Share how the new tools can help them with practical things they are currently doing or plan to do - don't just throw a bunch of new stuff at them.
If I recall more, and can get it organized so it's easier to follow, I'll come back and post it. Saving Changes...
Christine NielsenSenior Project Manager| Alberta Health ServicesCalgary, Alberta, Canada
Hi everyone, I am undertaking a Microsoft 365 Program that includes Office, OneDrive, Teams, 32-bit app remediation, etc. Curious if you have a MS Project template or any tips on key learnings now that you are likely well underway on this project (beyond the great tips above - thank you). Saving Changes...
"If you have an important point to make, don't try to be subtle or clever. Use a pile driver. Hit the point once. Then come back and hit it again. Then hit it a third time--a tremendous whack."
Community Champion
