Forum Discussion
Grouping applications for sequential deployment
Hi All,
We're currently deploying Office 365 for a global organisation of around 15,000 users, and I'm looking for some advice on how best to sequence the applications we're deploying.
We've decided against a big bang approach, largely because the nature of the organisations means it would be very challeneging for the end users, however was wondering if others have any best practice advice/tips for how to group and deploy applications?
The main areas of interest are:
- Which applications would you group to achieve the best synergies (e.g. need SharePoint to use Teams)
- How long would you recommend waiting between deploying groups of applications?
Thanks!
Hi Jonny Slater,
Interesting questions.
Rather than looking at delivering technology I would look at delivering solutions fro each business need. So I would collect all the needs that your 15k users might have and then implement the solutions/application as you find that you need them. e.g. If everyone needs a place to put their document then implementing Microsoft To-Do first doesn't make much sense.
Putting a force number of weeks between the introduction of applications doesn't make much sense. e.g. if you highest priority is MS Teams then waiting with SharePoint doesn't make much sense as people will just wait until they can properly use the really needed MS Teams.
