Forum Discussion
Solved
Review of Ignite 2018 roadmap for SharePoint
Having had a quick review of the Ignite roadmap issued in September together with the Microsoft 365 roadmap and blogs here I'm quite surprised that so little was released to Targeted Release this week. Either the next two weeks, I won't count the holidays, will be very busy or we are slipping into 2019. Now, the initial response might be: does it matter? I understand this from a quality perspective but updating the roadmap, which still shows October launch dates, needs to be addressed. What do others think? I hope I can eat my words next week 😉
I understand that feature deployment is a complicated process, what I don't understand is why it is hard to have a checklist with the following items:
1. has roadmap update been readied for publication
2. has announcement for Message center been drafte
3. has blog post been drafted
If no to any, the deployment is put on hold
3 Replies
- I think it is all too typical of the communications around changes. The can't even clearly identify which changes are going to be in the Targeted Release program and most of the services/workloads/apps don't even use this program. The concept is appealing but the actual implementation of targeted release in O365 leaves a lot to be desired.
- Agreed. The focus on marketing in 2018 has been exceptional but seemingly beyond reliable execution. A single, accurate 'version of the truth' is required. I even rely on Twitter and still we're not achieving a good view of deliverables. I have a very high regard for the team and high tolerance for the 'buzz' but work announced sets an expectation. From a service perspective we do pay so a delay in delivery is actually a 'cost' to a customer. The wonderful world of cloud computing I suppose!
I understand that feature deployment is a complicated process, what I don't understand is why it is hard to have a checklist with the following items:
1. has roadmap update been readied for publication
2. has announcement for Message center been drafte
3. has blog post been drafted
If no to any, the deployment is put on hold
