Hi Prateek Sharma,
Thanks for providing some information that clarifies things somewhat. This still leaves a lot of questions and I suspect anyone who uses Project Accelerator for portfolio management is going to have similar questions. for example:
- If this new planner release has a feature that allows a Planner instance to be migrated to a Project for the Web instance as has been described, does that mean a plan will then be set up in Project for the Web and consequently the data will be migrated to the P4W Dataverse and into Project Accelerator?
- What is the process for this?
- How can it be governed by portfolio managers to ensure that people aren't just pushing projects into P4W without any control?
- Are there future changes in the roadmap that could impact Project Accelerator as these other products develop and converge?
- What does this mean for licensing and user administration?
- Will I need additional resources to deal with user wanting to migrate and change their license and project delivery processes?
Portfolio and project governance specialists have processes and controls governing project workflows that take into account how the different platforms we operate off work and how the tools interact. These types of changes have impacts on process, governance and user expectations that need to be planned for in advance.
Add to this that we are looking the Viva Goals which also has interoperability links with Planner and P4W, it's own reporting features and we have our own reporting in Power BI we have invested heavily in. It is important for anyone who uses these products at an enterprise level to understand in more detail what the impacts of these changes are.
To be frank, It feels like Microsoft is communicating on these changes to Planner as if they are upgrading a consumer app when the fact is that this is a feature change to a component of a complex integrated suite of tools that are marketed as enterprise grade.
If Micrsoft want to play in the enterprise PMO space, then I think they Enterprise PMO managers should be communicated to with more than a banner in an app screen and consumer level discussion in a blog.
I would like to see some detailed information on the timing, architecture changes and data migration processes as a starting point, so we can be better prepared.