Overcoming Limitations in Project for the Web: Practical Solutions

As Project for the Web (PFW) continues to evolve, Microsoft is consistently introducing new features to enhance user experience and functionality. However, certain robust capabilities from Project Online remain absent in PFW. In this blog post, we’ll explore some key limitations of Project for the Web and propose actionable solutions to help teams maximize their project management efforts.

1. Project Baseline

One of the significant features missing in PFW is comprehensive support for project baselines. A project baseline is essential for tracking progress against the original plan, and while PFW offers partial functionality, it falls short for organizations needing multiple baselines.

Solution: To implement a custom baseline solution, you can create two new tables: Project Baseline and Task Baseline. Include all relevant columns necessary for your baseline tracking.

Next, create a custom button using the command bar to facilitate data entry. You can use Microsoft Power Automate to build a flow that reads values from the Project and Project Task tables and populates the corresponding Baseline tables. This setup allows for the integration of baseline data into Power BI reports, enabling users to analyze variance and performance against the established baselines effectively.

2. Task Limitations

Currently, Project for the Web restricts projects to a maximum of 1,500 tasks. This limitation can hinder larger projects that require a more extensive task list to capture all necessary activities.

Solution: To work around this constraint, consider using Programs as a structural unit. Break down the larger project plan into smaller, manageable sub-projects, each with its own task list.

Create a Program in PFW and link all the smaller projects to it. This approach not only helps in managing tasks more effectively but also allows for the aggregation of data across all projects within the Program, giving stakeholders a comprehensive overview of progress and resource allocation.

3. Timesheet Management

The absence of a robust timesheet feature in Project for the Web can be a significant drawback, especially for teams that rely on tracking time and resources against project deliverables.

Solution: To address this limitation, leverage third-party timesheet applications available on the App Store. These apps can seamlessly integrate with your existing PFW setup, enabling team members to log their hours and project managers to review progress effortlessly.

By utilizing these applications, you can ensure accurate time tracking, improved accountability, and better project management oversight.

Conclusion

While Project for the Web continues to grow and adapt, understanding its limitations and implementing effective solutions is crucial for maximizing its potential. By creating custom baselines, structuring projects into manageable programs, and utilizing third-party apps for timesheet management, organizations can overcome these challenges.