Microsoft Project Server Reviews

The most useful feature of Microsoft Project Server is you can select a function to see the baseline.

The price of the solution could be reduced.

I have been using Microsoft Project Server for approximately 15 years.

We have approximately 100 to 500 users using Microsoft Project Server.

The support we have received is good.

Microsoft Project Server is more expensive than other solutions on the market. We purchase the license annually.

I rate Microsoft Project Server a ten out of ten.

We are using it for building Research and Development Project labs.

It has been helpful for calculating the time of completion of our projects and looking at the critical parts of our projects.

The ability to look at resource loading is most valuable.

Collaboration within the tool is lacking when you compare it to online or cloud-based tools.

We should be able to notify assignees about the tasks that have been assigned to them. This is something that we don't have, and it could be because of the way it was deployed for us.

I have been using this solution for about five years.

It is pretty stable.

It seems scalable to me.

I don't have any experience with them.

It was our company's decision to switch to this. With my previous employer, I have used different solutions. Smartsheet is one of them.

I did not deploy it myself. I am an end-user. We have an IT organization for its deployment.

You have to define your use case and see if this tool makes sense for your use case or not. 

I would rate it a seven out of 10.

We are currently using the 2001 version. 

We use the solution for projects, with the goal of it being shared with more users, who can employ it as a single tool. 

The solution could have more compact dashboards, such as one finds with Planview. 

We have been using Microsoft Project Server for 20 years. 

The solution is stable. 

The solution is scalable. 

I cannot comment on the technical support as I was not directly aligned with it. 

I cannot comment on the price as I was not responsible for purchasing the solution. 

The solution is easy to use. My advice is that one first try it out, guage its look and feel. 

I rate Microsoft Project Server as an eight out of ten. 

I use Microsoft Project Server to create project timelines and task tracking.

The most valuable feature of the solution is that it is easy to understand and navigate.

Stability of the solution is an area with certain shortcomings where improvements are required.

I have been using Microsoft Project Server for two months. I only know that I use the solution's web version.

Stability-wise, I rate the solution a seven out of ten.

It is a scalable solution.

For project management, I use Asana and Trello.

The initial setup of the product is easy.

The time taken for deployment of the solution depends on the pipelines.

The product's installation phase can be carried out by one of the in-house teams in my company.

I recommend the solution to those who plan to use it.

I rate the overall tool a seven out of ten.

I am using Microsoft Project Server for managing projects, such as all the tasks-related activities are tracked.

When a project is complicated this solution monitors every task allowing us to have better control of the projects.

The most valuable feature of the Microsoft Project Server is the level of detail with which I can break down a task and check the dependencies.

The solution could improve the ease of access could improve. It can be time-consuming.

I have been using Microsoft Project Server for approximately one year.

I rate Microsoft Project Server a seven out of ten.

We primarily use the solution to manage the project lifecycle. Generally the lifestyle starts at demand phase. We design a workflow according to customer's needs. The workflow starts with project ideation and project selection, if the project fits company criteria it will move onto the project management phase.  

Let's say you have 10 projects and you don't know which ones to move into actual project management phase. Customers use the portfolio and analysis feature of Project Server, and decide which project to do according to capacity planning(if they have the resources) and budget. If the company has enough resources then its the projects with most benefit that gets selected. For the selected projects lifecycle will continue. As it moves forward, you will get more project detail pages, more things to work with. This will also produce some reports as well.

The solution is very good at helping you pick which project to move forward with.

The stability has been pretty good.

We've found that the solution can scale if we need it to.

The installation is fairly straightforward.

The documentation on offer is excellent.

Technical support is very responsive - particularly on critical tickets.

When it comes to integration with other systems Project Server falls short. There used to be out-of-box integration with TFS for example but with Project Server 2016 and forward that integration is deprecated. There is room for improvement here.

When it comes to project management itself, I'd like to see some hybrid solutions right now across the on-premises deployments especially. On-premise only has waterfall style project management. On the other hand Project Online has a lot better integration and hybrid (agile-waterfall) project management abilities. This should also be the case for On-premise customers.

The check-in, check-out feature, makes Microsoft Project Server pretty slow or cumbersome to use. Users mostly forget when to check-in. We have problems with that. If it's a bit faster to use, or easier to use, like your Planner or other programs, it would be better. You should just be able to type in something and it's updated. The ease of use could be improved.

I've been using the solution for three years at this point.

The stability is okay. There aren't bugs or glitches. It doesn't crash or freeze. It's reliable.

The scalability is okay. We don't really have any technical performance problems. If we have it, it's because of infrastructure, not because of Project Server mostly.

We mostly work with governmental agencies. On current projects, there are about 300 people working on the solution. We have ten project managers and five profile managers on our end.

Technical support is pretty good. We have seen problems due to the infrastructure and management on the customer's side, which affected some services on Project Server. One ticket I opened as normal severity which took two weeks to resolve. That said, when I opened a ticket with critical severity that is blocking some services, somebody contacted me in less than an hour. We were able to fix the problem in three hours total. I'd say overall, the support side is good. 

There's also excellent documentation, which I would rate at a nine out of ten.

The installation is very easy with MinRole helping you along the way. You can do high availability of the SharePoint services fairly easy except for the DB part. For that you have to rely on your DB Admins to give you a listener for a High Availability cluster. 

I'm not just a user, I implement solutions. We are Microsoft partners. I develop the solution from infrastructure to power bi reports. User experience, customization, and reporting.

In Turkey, especially governmental agencies, they don't want to be on the cloud. So all the environments I manage, they're on-prem.

Overall, I would rate the solution at an eight out of ten. We're mostly happy with the product.

We use it for master project scheduling, that is, the first schedule of each project.

I like the way you can build the schedule by the Don't Start Before or Don't Start After values. You can use it to build your schedule based on how you change your dates. This is how it actually builds the schedule.

It needs to be more collaborative from inside the application. It only does project scheduling for me. It would be good if it could do other things and be more collaborative, such as sharing tasks for users. 

It is not really incorporated into MS Office, so you can't copy-paste stuff. It is on its own, doing its own thing. It is only used for scheduling, and it doesn't work well with anything else.

I have been using Project Server since it came out almost 20 years ago. In my current company, I have been using it for two years.

It is stable.

It is scalable. It appears that you can scale it as much as you want. 

We have 70 or 80 licenses, but in reality, there are no more than 10 people actually using it.

The initial setup was complex.

It is on the expensive side.

It seems to me that it is the standard for doing project scheduling, which is a shame. It should be used for more. You should be able to do more things with it because now it is not enough for people to just build a schedule and then use something else to do your daily planning. I used to work for Microsoft, so I know how these things were built. I know some of the issues they have. It seems to me that it is a product that was built on its own. It is very standalone, and it hasn't been incorporated into the Office suite or other things that Microsoft products do. For example, we work a lot with Microsoft Teams. Microsoft Teams would be a nice front end to an MS Project.

I would rate Microsoft Project Server an eight out of ten.

• Project metrics
• Document management
• Financial reporting
• Resource management. 

We use the data collected to manage project data, create and manage assignments and schedule via MS Project connectivity. We also track the current and future assignments for our resource to determine their availability and workload for current and future endeavors.

One source of truth for project metrics, management, and financial reporting. Through additional dashboards and reports, we have developed a way we can distribute project data and updated it to all of our stakeholders and customers.

• Project management
• One consistently updated and backup/secured location for all project data
• Accurate project metrics are critical to being able to manage our projects from a central database.

OOB reporting is not very robust. We have utilized SSRS, Excel Services and Qlik Sense to expand the OOB reporting capabilities. We use a hosted on-premise version so that we can have better direct access to the SQL server data. 

MS Project standalone version and SharePoint repositories were our previous solutions.

Engage an experienced and highly rated vendor to help in the discovery and planning of the implementation. Project Server is better priced than many of the higher-end project management solutions.

No.

Training for the userbase is a primary concern. Make sure there is a great training plan in place to ensure the userbase can be productive very early in the process.