Following the publication of my article on Surfing the Office 365 Waves: an Office 365 Roadmap Analysis with Power BI in March 2018, I have got an incredible amount of positive feedback. I continued to analyse and follow Office 365 roadmap, and the impact of latest announcements on it (especially SharePoint innovations transform content collaboration with mixed reality and AI). I discover on each of my public talks that people in the industry are not really well aware of fundamental changes that have arisen in the last years concerning new software and services conception, and especially for Office 365. In particular, the MVP (Minimum Viable Product) concept, which I think is essential for a correct understanding of the platform, is still little known.
So here is a good time to update this article with new information.
1°) Technological waves described in the Dion Hinchcliffe schema below are more than ever, truly identifiable topics.
But what amazes me in the schema is the perfect match we can find between technological waves (above) and Microsoft products strategy (schéma below – thanks to Julie Bredèche – présented in French at SharePoint Saturday Montréal)
Since the first publication of my post in March, SharePoint Spaces were announced and this confirmed that virtual reality and augmented reality (which at some point sounded like Science Fiction in the Digital Workplace space at least), are making their way toward end-users and widespread usages. It is after all a new means to create dynamic and impacting contents.
2°) The MVP (Minimum Viable Product) notion that I presented at SPS Zurich (English), European Collab Summit (EN) and SPS Montréal (French), is largely unknown. However, it is fundamental to understand how innovations are added to such a big platform as Office 365. As such it should be taught at all schools.
In a few words, it is a product development strategy that allows creating a product with minimal functionalities in order to put it without delay on the market and then to improve it with quick iterations. This approach is directly connected to agile methodologies that make such an approach possible and manageable. Adding new features to the product is driven not only by user feedback (user-voice) but also usage data collected on the platform that allows validation (or non-validation) of the benefits of new features. It will be validated only when proof of efficiency to solve a specific need is made.
Here is the best picture I found on what is this approach all about.
3°) I updated my Power BI report where I analyze Office 365 roadmap with data valid as of June 10th, 2018. Here are the first insights: