Microsoft Project Server Reviews

The solution was used to prepare documentation and manage the project timelines and schedules. We used the tool for documentation control and project management. We can manage and create budgets, timelines, and schedules. We can know when we are lagging, when we are on time, when we have to change the resources, or when we have to manage our resources differently. We can get all the reports from the software. We used the solution to manage multiple projects.

The scheduling feature is the most useful. Gantt Chart, scheduling, and project tracking features significantly helped our project tracking needs. We can download in Excel, PDF, and other formats. The solution can be integrated with all Microsoft tools like Microsoft Excel, Microsoft Word, and Power BI. Since the product is integrated with Power BI, it has good business analytic features that businesses can use.

The learning curve is quite easy. The product is quite easy to use and understand. I was trained for 15 days and could use whatever feature I needed. We did not have to do much to learn Microsoft Project Server because the icons and the tool palette are quite similar to Microsoft Excel and Word. We could easily understand it.

The solution must provide Agile and AI features. It will help users benefit from the latest technologies.

I have used the solution for two or three months.

I rate the stability a nine out of ten.

I rate the tool’s scalability between seven and eight out of ten.

The initial setup is straightforward. It's quite easy. One person with the right knowledge can set up the software. Microsoft’s team is available online to help us with anything we require.

SAP is complex to learn, but Microsoft Project Server is not complex.

Some tools are quite difficult to deal with. We have to remember the codes to learn SAP. Around 55% of the industry uses Microsoft Project Server as a project management tool. I will definitely recommend the product to others. It is one of the best tools someone can have in the construction industry. Overall, I rate the solution a nine out of ten.

Most of the servers from Microsoft are used because of internal stakeholders' demands. With Dynamics 365, my company used an ERP tool. My company uses Microsoft Project Server as a tool to run various projects.

The most valuable feature of the solution stems from the fact that the tool's reporting is very good. The tool helps with better project management, allowing you to plan projects.

The product's UI is not very user-friendly. From an improvement perspective, I want the tool to offer a user-friendly UI. Microsoft should attempt to match the capabilities offered by the other players in the market.

Microsoft Project Server has issues with SharePoint, providing a not-so-user-friendly experience to users. The aforementioned area can be considered for improvement in the product.

The high cost of the product is an area of concern. The product's price could be made lower.

I have been using Microsoft Project Server for five to six years. My company provides the solution to our customers.

It is a very stable solution. Stability-wise, I rate the solution a ten out of ten.

It is a very scalable solution. Scalability-wise, I rate the solution an eight out of ten.

Most of the company's customers prefer JIRA.

The solution's technical support is very good. The response from the product's support team takes less than twenty-four hours.

The product's initial setup phase is easy. It is not easy to work around the product.

The solution is deployed on an on-premises model.

The solution's deployment takes less than five minutes.

The product is expensive.

For scheduling and resource management of our company's projects, we use JIRA and Microsoft Project Server.

The reporting and analytics part of the product is very good.

The integration capability of Microsoft Project Server is phenomenal, and it serves as one of the reasons why the product has been holding up in a good way till now in the market.

For certain use cases, Microsoft Project Server is a good product. I would recommend the product to others who plan to use it since it is good when it comes to analytics and reporting.

The value or positive impact of the use of the product stems from the fact that it degrees with other products like Office 365 and other Microsoft solutions. Microsoft Project Server has been in the market for a long time. Over a period of time, I have seen a lot of features introduced in Microsoft Project Server. I believe that the product still has room for improvement.

I rate the overall tool an eight out of ten.

I use Microsoft Project Server for basic product deployments involving API.

The most valuable feature of the solution is that it is stable to use, especially since I work with Microsoft for an extended period. Microsoft Project Server is pretty convenient for me to use since I don't have to pay for it.

There are certain shortcomings in the documentation part where improvements are required. Microsoft should release some basic documentation on use cases to the public so that anyone who wants to learn more about the product can learn about it through the documentation available on Microsoft's websites.

I have been using Microsoft Project Server for a week or two.

It is a stable solution.

It is a scalable solution.

Around 100 people use Microsoft Project Server.

The initial setup of Microsoft Project Server is easy.

If the codes and everything else related to the deployment process are ready, then the completion of the deployment phase would hardly take 20 to 25 minutes.

The solution is deployed on the cloud.

Microsoft Project Server provides users with all the tools necessary for deployment, so you don't need to seek any external help to install it.

There are some payments related to the licensing cost of Microsoft Project Server.

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

I rate the overall product an eight out of ten.

We use the solution for project consolidation and project portfolio management.

I found the portfolio management valuable.

Resource management has room for improvement because it uses a lot of resources. We used to use Star BI, and everything else was an additional cost to our business. We also had to pay extra money for reports.

I've worked with Microsoft Project Server for ten years.

I rate the solution's stability a five out of ten because we had major issues with the Sharepoint part. The problem was not with the Project Server.

I rate the solution's scalability a ten out of ten. The solution is meant for medium-sized enterprises.

The online support is useless. It goes into a loop. For example, if you go into "options," it sends you back. You go into this constant loop of trying options. The online support is terrible.

The initial setup for Microsoft Project Server is complex.

We implemented the solution in-house.

I rate the pricing a one out of ten because the price is way too high. You need five enterprise server licenses, then an SQL Server in addition to that.

We used some of the functions, but part of the reason we stopped using it was because of the cost. We chose an on-prem deployment because of problems with bandwidth. I wanted to perform software backups, but the connectivity was down, so my whole operation would stop if I went on the cloud.

I rate Microsoft Project Server a seven out of ten. I love the solution and enjoy working with it, but the cost is an issue, and the documentation is terrible.

Currently, we are helping a government entity with their PMO portfolio. They have many departments and streams. The main Microsoft Project Server use case for them is managing the planning for all the projects within the workflows, monitoring the projects inside the dashboards of the PMO and processing all the workflows for the project initiation, charter, and deliverables.

There are many valuable features of this solution. It is very advanced and once you understand and learn how to use it, it can be quite powerful. The whole package can be quite powerful. Inside of Microsoft Project Server, you not only have in-house development solutions, but also the workflow engine. You can create templates, pages, and users. The web part is very straightforward and even without any development knowledge, you can create any page you want aside from the workflows. This is fantastic.

The solution should be made more collaborative. Currently, we are using Microsoft Project Server alone, without the involvement of a team. In other words, we are not collaborating with the whole team within the solution and that is a minus. 

I would also like to see an integration with Amazon's project management solution. As of right now, there is no integration. We have a link only between the Amazon project management solution and the planner activities. This is very basic and we need some advanced cooperation options.

I have been using Microsoft Project Server for four years.

I would rate the stability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best. My opinion is that the cloud version of this solution is quite stable.

I would rate the scalability of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best.

The main problem with this solution is collaboration between teams. If you want to involve the other teams you'll have to buy Project Light servers or enable the project team members to collaborate inside the plan itself. This is an extra cost to the standard license. We also have a license for the planner and the teams, but we need some integration between all of them.

The professional and premium licenses are quite expensive.

The solution can be very slow. Sometimes, it takes minutes to open a page that shares the dashboards. 

In addition, there is no training material and there needs to be more awareness training. There's no online help to aid users through the process.

The first thing I would say to anyone trying to use this solution is that you need to understand its capabilities and functionalities before trying to use it. If you are not aware of the capabilities and features, you are using a Bugatti like a normal car. You need to get the right training and educate all of the project managers on how they can utilize the main functionality and services of the solution.

Overall, I would rate this solution a seven, on a scale from one to 10, with one being the worst and 10 being the best.

I am a Project Server Administrator and BI Analyst. I work extensively with Microsoft Project Server. We are currently on the 2013 on-prem version, which is currently two versions back. We are in the process of migrating to Project Online, which will in the Microsoft cloud.

We use Project Server to track enterprise-level projects and implement projects. As a financial institution or credit union service organization, we have over 1,800 member credit unions. We use Project Server to manage our enterprise projects where we're building, modifying, and maintaining products, which are then implemented by our implementations teams. They use Project Server for their checklists and for their project management during implementations. We also use it to track costs in our enterprise projects.

It brings all the information and all the data about our projects into one location. It helps us in providing holistic reporting and trends analysis across projects through the entire enterprise.

Project schedule management is very good. Basically, it sits on SharePoint. So, every time we create a project, a new project site is created within that SharePoint environment, which is a very good document repository. It allows us to create issues and risks lists and additional functionality to keep track of what's going on with projects.

The reporting aspects can be improved, which is one of the reasons why I'm using Qlik Sense. In the older on-prem versions, reporting was lackluster, to say the least. Project Online has a better handle on that. However, we will still be using Qlik Sense as the licensing model for native PowerBI reporting is a bit restrictive and expensive for a small enterprise(under 250 users of the tool). We're also looking at an add-on app from OnePlan that adds additional functionality and thord party app connectors as Microsoft is not as clean in its approach for functions such as portfolio management and some of the trend analysis we need.

At this company, I have been using it for about seven years. I've also used Project Server in different organizations previously. 

It is very stable when it is properly configured. When it is not properly configured, it can be a nightmare, just like many programs. In terms of moving to Project Online, we expect a lot better stability. That's because it is being managed by Microsoft, and it will be under their control. We'll be under their supervision. They're going to make sure that it runs properly because they'll have thousands of clients running the same software at the same time, so they've got to be stable across the board. The current on-prem is reasonably stable. It is just we've outgrown it. It is two versions behind, and we need to get into a better situation for the long term.

The older on-prem versions are not as scalable as we would like. Performance starts to suffer a bit when you get too many projects and too many resources in it, but Project Online is supposed to be much more scalable. In fact, we won't have to really manage that side of the house at all. It is going to be a matter of Microsoft keeping things running well and us just not pushing configurations that are unusual.

Currently, we have about 1,600 users. They are different aspects of the business, such as IT, project management, etc. The usage of the older versions that are on-prem is decreasing simply because Microsoft is pushing everybody to the cloud. The on-prem versions are still out there. There are still a lot of large organizations that like to stay on-prem because they like to have better control over their data. It has a pretty widely used set of applications across the entire spectrum, but the on-prem servers and such are starting to migrate more toward Project Online.

We're primarily working with our vendor, and they've been very good. We've had no real problems with them.

There was a partial implementation of Primavera, which was primarily used by our IT group for timesheets. We were probably only using 5% of the capabilities of the product, but in terms of cost-effectiveness and overall usability within our infrastructure, Project Server became a better option. Prior to that, we had standalone project plans using MS Project, a standalone client, and spreadsheets.

It was complex. It took us months, but that was primarily because we had a very stripped-down version. It was basically a quick standup for us that was not properly configured. When we went really committed to the platform, we had to undo a lot of stuff and do a lot of analysis in order to make sure that we were reconfiguring the product into a usable state for ourselves. So, a good chunk of that month was in terms of analyzing business processes and options.

In terms of maintenance of our on-prem version, our vendor handles 90% of maintenance. I don't think they end up having to do quite a lot. It is mainly keeping the servers active, and currently, that system is out of support. So, it is mainly maintaining the operating systems on the servers and just watching disk drive space, etc. In terms of maintenance within the system, we probably put in four to five hours a week for just maintaining resource profiles, answering questions, and providing general support for the user base.

We use consultants. In fact, our current on-prem solution is hosted by our consulting vendor, and they manage all of the systems on the AWS cloud. Our experience with them was good. In fact, we are using them to help us migrate to Project Online at this point.

I'm not quite sure about the licensing costs. We're probably paying somewhere in the neighborhood of about 80,000 to 90,000 a year for our current on-prem because we handle our own licensing. As far as Project Online is concerned, we're still trying to get a good handle on that. It looks like it is going to be in a neighborhood of about 120,000 to 150,000 a year, but we're getting a lot more capability out of it.

We have an enterprise agreement. We've got a pretty large enterprise using the whole suite of Microsoft products. We have probably somewhere in the neighborhood of 2,600 to 2,800 people who are using either Microsoft OS, Microsoft Office, Microsoft Exchange, or something along that line.

Planview, ChangePoint, Monday.com

The biggest item of advice would be to really understand your business and what your real needs are and then compare Microsoft Project Server or Project Online to some of the other offerings out there. If you are going to be in a more robust and complicated set of project processes, Project Server is probably a very good fit for you. If you're only into lightweight project management, it may be a little bit overkill.

I'm still trying to get a feel of the overall functionality of Project Online. We are going to be putting an add-on product on top of it to kind of fill in some of the gaps. 

Currently, I'm going to rate it an eight out of 10. 

We use the tool in our IT-related projects. All IT efforts are managed using the Microsoft Project Server. Every week, we have a project status meeting where we demonstrate the project's status using the tool. We track tasks and progress, assign owners, and monitor milestones and all project-related work using it. 

We sometimes need support from the IT department for installing and deploying the Microsoft Project Server. It is not user-friendly, and users cannot install it themselves.

I have been using the product for four to five years. 

I rate the tool's stability an eight out of ten. 

My company has 30-35 users. 

We contact local partners for support, and their support is okay. 

The tool's deployment is not difficult. We centrally deploy the Microsoft Project Server for the project owners, and we manage projects in our data center using it. 

Our ROI is good. 

We have an enterprise agreement with Microsoft, and our licensing is based on the agreement. 

I would recommend the tool to others and rate it a ten out of ten. We use Microsoft Teams for collaboration. 

The main use case was related to task management, involving the assignment of tasks across departments. It provided visibility into individual performance, allowing for team member invitations, and monitored key performance indicators.

Our experience with Microsoft Project Server wasn't very positive, and due to high demand, over 70% of employees requested to stop using it. They encountered technical difficulties and faced challenges with the customer helpdesk. Getting in touch with a representative for assistance was a prolonged and frustrating process.

One notable positive aspect is its effective project-tracking capabilities.

Remote usage and tracking pose challenges, requiring navigation through numerous technical details and troubleshooting. This inconvenience sometimes leads to abandoning the task on the device and waiting until the next workday to resume operations. Improvements are needed in the technical support process, aiming for a better user experience. The current process, when encountering difficulties, should be more user-friendly, streamlined, and efficient. Quick and accessible customer support is crucial, especially when seeking assistance during work hours.

I have been working with it for eleven years.

The stability was consistently problematic and we experienced frequent ups and downs with the MS Network, encountering issues like lagging and having to restart the system. At times, the problems were more severe, requiring a full computer restart due to the software freezing and affecting the entire computer screen. While these issues didn't occur daily, they were a recurring problem, happening quite often. I would rate it four out of ten.

I would describe it as moderate for my team. It's manageable, but it doesn't meet our expectations fully. On a scale of one to ten, I would rate it a five. We have approximately three thousand users working with it.

Our experience with its customer support services wasn't satisfactory at all. I would rate it two out of ten.

Negative

Asana and monday.com provide faster customer service responses compared to MS Project. Among them, monday.com stands out for its promptness, while both surpass MS Project in responsiveness. This highlights the need for MS Project to enhance its support system and streamline the user experience in handling technical challenges. MS Project's speed falls below expectations; it's notably slow and often requires reloading. The dashboard is not user-friendly, leading to considerable time spent on training people to use it effectively. In contrast, Asana and monday.com stand out at the top of the league in terms of speed and user-friendliness.

The initial setup was notably complex, in contrast to Asana and monday.com, which offer more simplicity and user-friendliness.

For those looking to work in real-time and seeking a faster and more accessible project management solution, I strongly recommend considering top project management software. Opting for cloud-based solutions with features for both project and portfolio management is crucial. There are several options available, such as monday.com and Asana, and even tools like Trello and others. Overall, I would rate it four out of ten.