Microsoft Project Server Reviews

• Ease of use.
• Adaptability.
• Stability.

• The centralization of all projects baselines in Project Server gave us control over the process. Additionally, we unified the information into just one source to report indicators, progress, milestones, and much more.
• Microsoft Project Server gave us an easy way to list and classify our projects, creating great views for a high quantity of information with the Project Web Application.
• We can now define our own project indicators and performance KPI’s, according to our project process. During the last 4 years we have used Project Server to save more than 400 baselines.

I think that "earned value calculation" could be improved, and also the relationship between time and cost, that sometimes does not allow adjustments during execution.

I have used this for 10 years.

I did not ecnounter any stability issues.

There were no scalability issues. We have more than 400 projects on our Project Server database, and everything works fine.

Technical support was adequate.

We did not use any previous solution.

Initial setup was hard work, but I wasn't involved.

Scope your needs carefully, in order to get exactly what you want.

We did not evaluate alternatives.

I wasn’t involved during implementation.

The project management, scheduling and resource management features are most valuable to us.

It has improved the structured PMO process and implementation in our organization.

The stability and performance in enterprise-grade farm implementations needs to be improved.

I have been using the current version for the last four months. The old versions I have used for around six years, i.e., 2010 and 2013.

There are issues with bugs and things break, when the scale is increased.

We encountered scalability issues, i.e., the features were breaking.

I would give the technical support a 8/10 rating.

Previously, we were using a different technology.

The setup process requires technical operations.

You should buy as much as is necessary.

We did not evaluate other options but we have used other similar tools.

Planning and expertise is required.

Microsoft Project Professional is the best client application (and is also used in competitors’ solutions) because it has:

• Good scheduling engine
• Nice reports in the latest version of the product

It gives us a clear view for the whole portfolio of our projects.

• Resource reservation workflow
• Financial management

I have used the Microsoft Project Server (and MS Project Central) platform for 10 years.

I only encountered stability issues with the 2010 version.

I only encountered scalability issues with the 2010 version.

The number of partners offering support is one of the highest for PPM solutions.

I did not previously use a different solution. I have always used Project Server.

Initial setup is not as easy as it looks on first impression.

This is probably the cheapest TCO enterprise PPM solution on market.

Before choosing this product, I compared it to Planview and HP PPM.

I advise not doing it by yourself; use an experienced Microsoft PPM Partner.

This product gives the ability to have all project data in one location and look across information while still giving PMs the flexibility to manage their project and have a tool to use with their team (fine balance between project management tool and management tool).

• Views can be controlled organization role.
• Custom attributes can be added as trigger levels to include in a management report, view or dashboard
• The use of SharePoint allows team collaboration and gives the PM the flexibility to add document libraries, lists, etc. to manage their project.

Dashboarding of information has given the organization insight, so we can move to be more proactive versus reactive.

Risk Management: Risk and issues are stored in the project SharePoint but there is no real auto communication of assignments (unless the end user sets it up); there is no mechanism for automatic escalation (much needed).

Issues are visible within the application (My issues area) so individuals can log in and see issues assigned to them.

Project Managers can set up email communications when issues change. (Admin can’t do it across the board but individual PMs can set up.)

We flag issues that need to be escalated and use SSRS reports that are emailed out at regular intervals.

I implemented Project Server in November 2014 (and have used MS Project since 2000).

Nintex workflow integration does give us some performance delays. Workflow response times can take up to 20 minutes to proceed to the stage (this is a work-in-progress for our IT team).

I did not encounter any scalability issues.

Technical support is 8/10.

We used Business Engine Network for 12 years. Business Engine Network was bought by Planview and sunsetted. We were geared up to implement Planview’s product when the opportunity arose for us to look at MS Project Server. While Planview is a great portfolio management tool, its project management is weak.

We used a third-party supplier, Pcubed, for initial setup.

Pricing varies according to many variables (on premise, MS hosted, third-party hosted, etc.)

Having a PM business process in place prior to tool implementation to support that project not only makes it easier to configure the tool but makes it easier to grow the tool and become more mature in your business process.

There are a few valuable features for us, including the dashboards, the reports it can generate, the projects function, and the timeline feature.

It's certainly increased our productivity. It also helps each of our business groups with maintaining transparency and to keep track of projects and tasks. We're able to share information with each other as well.

There are formatting issues that haven't been resolved. This needs improvement as it's annoying.

We haven't had any issues with deployment.

We haven't had issues with stability.

We haven't had issues with scalability.

It provides us with complete visibility of resource allocation on a global team.

It forced the organization to implement standard project management practices.

Make transitions easier to implement, e.g. if a new portfolio comes along, it should be easy to integrate to the existing portfolios.

I've used it for less than one year.

No issues encountered.

No issues encountered.

No issues encountered.

It's good.

It's good.

No previous solution was used.

We used a vendor team.

We've not measured it.

We also looked at SAP PPM.

Plan, plan, plan. Make sure you understand your organizational needs and you know the process forward and backwards. The software is just a tool, if you do not understand what you're fixing, there is no way the software will help.