Microsoft Project

What differentiates Microsoft Project from other similar products?

It is distinct from other programs due to the level of difficulty it might present, which necessitates an understanding of the functioning tool.

What is your favorite aspect of this product?

While Microsoft Project is a great tool for managing projects, whether or not to use it will ultimately come down to factors like scope and cost.

What do you dislike most about this product?

A complicated tool that must first be instructed on, in addition to being compatible only with Windows operating systems.

What recommendations would you give to someone considering this product?

This software comes highly recommended from me because of how well organized and straightforward its interface is. It's quite user-friendly, providing tutorials and instructions to get you started.

What differentiates Microsoft Project from other similar products?

Ability to store local copies of project plan's and is widely used. Plan's can be exported into various format's

What is your favorite aspect of this product?

The plan's can be duplicated to fit other projects, easy to add new tasks and dependencies has a lot of features

What do you dislike most about this product?

Sometimes too many features, planning can be difficult when its not clear what tasks could be impacting others and sometimes days not not add up which takes a lot of time to identify the cause.

What recommendations would you give to someone considering this product?

Trial the software and understand what features you need from Project and to assess if you need everything it offers.

What differentiates Microsoft Project from other similar products?

I have only had exposure to MS project / PWA and connot comment on how it compares.

What is your favorite aspect of this product?

Being able to connect it to PBI for senior management reporting and dashboards. A wealth of data is available in the tool, and provided it is set up and used correctly it is extremely effective at tracking programme or project statuses.

What do you dislike most about this product?

The breadth of fields to use can be overwhelming, and where sharepoint connects to the schedule for document tracking I feel that the access reporting falls over a bit. It is unclear who retains access to a project container once users are removed from the build team. In addition, if a project must be closed, removing access from the project schedule impacts the timesheet data, but not the sharepoint element, making it a very messy experience from a project governance perspective. This is particularly true when trying to remove access to prevent unintended document changes post project.

What recommendations would you give to someone considering this product?

Ensure that your organisation has a clear understanding of it's project governance as well as a medium tern roadmap to ensure the build / implementation does not stall due to poor planning. In addition, your organisation will need to understand the skills of those running the projects versus the system capability and ensure a balanced approach is found. Also ensure that stakeholders from all areas are included, as early feedback in input is critical in successful delivery. If you can achieve this, BAU will be simple and painless