The division I work in has 3 PMs that share resources. We have a three fold need we're trying to engineer a solution for within the Microsoft Office ecosystem.
- We need to create a resource allocation calendar for the entire division for the division manager. He wants to see the hours allocated per day per project for each of the 20 team members. Right now, the PMs handle this via ad-hoc chats to balance resourcing, but this isn't working with our offices closed for the foreseeable future.
- We need to keep our team members updated to their tasks and have a return flow on task updates from the team members to the PM/project plan. We cannot provide Project licenses to the entire team.
- We need this to be as easy as possible since we will be adding PMs as we grow and we want as much as possible for this to be automated.
Each of the PMs manages their projects via separate project plans and we are migrating to Project Online. We don't have access to PowerBI, which would allow aggregation across multiple Project Online projects.
I believe I can solve requirement 2 via a Flow path from Outlook to Project Online.
For items 1 and 3 however, I'm stuck and would love some insight or ideas.
I've investigated using Planner, but without the 2-way integration that isn't going to work. We looked at trying to use Flow to link Project Online -> CDM -> Planner, but that doesn't surface data properly that I can see.
I've considered going from Project Online -> Sharepoint -> Planner, but I can't get the start/end dates or resources into Planner properly via Flow.
I've looked at Project Online -> Sharepoint. This seems to work, but it is a flat task list instead of an Agile-esce bucket view like Planner and will require multiple Flow plans to manage everything Planner does on its own. This also doesn't handle task completion very well.
I've looked at Power Apps, but it appears to have limitations that prevents accessing data across multiple projects.
With all that being said. I'm really looking for any insights on how we can accomplish our needs within the Office ecosystem.