SamTech 365

Power Platform, Copilot & SharePoint guides by Samir Daoudi

Building a Project Management Solution in SharePoint: A Real-World Case Study

How we replaced InfoPath with a modern SharePoint project management solution for Rolls-Royce, plus how to build the same thing today with Power Apps.
Building a Project Management Solution in SharePoint

“Can we do project management in SharePoint?” is one of the questions I’m asked most often. The answer is yes, and done well it can look nothing like the SharePoint people are used to. In this post I walk through a real project management solution we built for Rolls-Royce on top of SharePoint, why we built it that way, and how I’d approach the same requirement today with the Power Platform.

The challenge

Rolls-Royce’s project teams were tracking projects with InfoPath forms on SharePoint. It worked, but:

  • InfoPath was obsolete, with no future and no modern user experience.
  • The native SharePoint interface at the time didn’t meet users’ expectations of a clean, intuitive app.
  • Notifications and reminders were manual, so deadlines slipped and project managers spent time chasing updates.

The brief: keep SharePoint as the platform the organisation already trusted, but give project managers something that felt like a modern web application, with automation built in.

The solution

A custom user interface on SharePoint

We built a custom front end with Bootstrap and SP.js (the SharePoint JavaScript object model), with SharePoint lists and libraries as the data layer. To users it looked and felt like a standalone app: fast navigation, clear dashboards and forms designed around how project managers actually work.

The home page: a modern project portal running on SharePoint
The home page: a modern project portal running on SharePoint
All projects in one place, with status, owners and key dates
All projects in one place, with status, owners and key dates

Modern forms instead of InfoPath

The InfoPath forms were replaced with custom forms that validate data, guide users through the required fields and save straight to SharePoint lists.

Creating a new project: a guided form that replaced the InfoPath version
Creating a new project: a guided form that replaced the InfoPath version

Automated notifications with Power Automate

We used Power Automate to handle the chasing:

  • Automatic notifications and reminders for project managers.
  • Alerts for critical deadlines and milestones.
  • Status-change notifications to stakeholders.

Centralised tracking and reporting

Project managers log, update and report progress in one place, giving leadership a single view of every initiative, including by location and by phase.

Project details: milestones, progress and key information on one page
Project details: milestones, progress and key information on one page
A location view helps teams see where projects are delivered
A location view helps teams see where projects are delivered
Grouping projects by phase gives a portfolio-level view
Grouping projects by phase gives a portfolio-level view

The impact

  • A much better user experience: users praised the interface, and SharePoint stopped feeling like “just SharePoint”.
  • Less manual effort: automated reminders replaced manual chasing.
  • Future-proofing: moving off InfoPath put the solution on a supported platform built on SharePoint and the Power Platform.

How I’d build it today

This project used Bootstrap and SP.js, which was the right choice at the time. For a similar requirement today, I’d usually choose one of these options:

Option Best for Notes
SharePoint lists + Power Apps + Power Automate Most organisations A fast low-code build, mobile-friendly, with flows for reminders and approvals
Dataverse + model-driven app Complex portfolios, security and relationships Richer data model and security, but needs premium licensing
SPFx web parts Deeply branded intranet experiences Full control over the UI, needs developer skills
Planner / Project for the web Task-level team planning Use alongside a portfolio app rather than instead of one

Whichever route you choose, the principles are the same: keep SharePoint (or Dataverse) as the single source of truth, design the forms around the project manager’s workflow, and automate every reminder you can. For the building blocks, see the Power Apps tutorial, how to create a form in SharePoint, SharePoint approval workflows and model-driven apps. If you’re still running InfoPath, the guide on modernising classic SharePoint will help.

FAQ

Can SharePoint be used for project management?

Yes. SharePoint lists and libraries make a solid data layer for projects, tasks, risks and documents, especially with Power Apps for the interface and Power Automate for reminders.

What replaces InfoPath forms in SharePoint?

Power Apps is Microsoft’s recommended replacement. For simple needs, modern SharePoint list forms with JSON formatting may be enough.

Should we use Microsoft Project instead?

For detailed scheduling, Project or Planner is great. For portfolio tracking, governance and custom fields across many projects, a SharePoint or Dataverse solution is often a better fit, and the two can work together.

Discover more from SamTech 365

Subscribe now to keep reading and get access to the full archive.

Continue reading