Microsoft Project Reviews

The primary use case of the solution is for in-house IT projects such as network projects, and system projects.

The most valuable feature of Microsoft Project is planning.

The licensing cost for Microsoft Project is expensive and has room for improvement.

The initial setup is complex and has room for improvement.

I have been using the solution for several years.

The solution is stable.

The solution is scalable.

The initial setup of Microsoft Project is complex.

The deployment took one day.

The implementation was completed in-house.

The license for Microsoft Project is a one-time payment but it is expensive.

I give the solution a six out of ten.

We have 20 people using the solution in our organization.

Two people are required for the maintenance of the solution including one manager and one engineer.

I recommend the solution to other users.

Our company uses the solution for project management. We monitor work progress or activities to ensure they are completed. We get a full view of start dates, end dates, and all dependencies required for actions. 

We store many things on Teams. We can make objections or put things in SharePoint. 

Nine team members in our department use the solution. Previously, we used only on-premises but now we are using both on-premises and the cloud service.

The solution is tightly integrated with other Microsoft products such as SharePoint and Power Automate and also integrates with Google.

It is easy to check project costs in the solution. 

Notifications provide alerts of new outages so you can move your project as needed.

The setup and scalability can be somewhat difficult for new users until they gain knowledge. 

Ongoing education would motivate users to learn and take advantage of the solution's many features. 

The price could be more flexible. 

I have been using the solution for three years. 

The solution is stable so I rate stability a nine out of ten. 

The solution is scalable. 

If you are familiar with Microsoft tools, then it is easy to understand the scalability. If you are a new user, then scaling may be difficult because you have to spend some time understanding Microsoft chronologies first to scale the solution. 

I have not used technical support. 

When we started working with the solution, the setup was somewhat difficult. Once you gain knowledge, you slowly see that the solution is easy to use. 

We implemented the solution in-house. 

The licensing model is somewhat complex. Initially, the price is low but scales up because you pay for consumption and usage. 

Pricing is okay if you have one or two users. If you add everyone in your company as project managers, then the price is high. 

The solution is better than Jira. 

I rate the solution an eight out of ten. 

Our company uses the solution for a project at our on-premises data center. We have one data room database and one mobile active account. 

We have 100 users in our head office who use Microsoft in our database and desktop application. A total of 5,000 employees use their mobile phones while working in the field. 

We will soon launch another project in the cloud. 

The solution is well established and runs very accurately. 

The solution is very user friendly so end users are satisfied. 

Project availability and speed could always be improved. Most of the time, we get the target from the system. 

If there is a chance to improve the interface, then it should be implemented. Otherwise, our end users are satisfied with using our own interface. 

Reports could be pushed more quickly. 

I have been using the solution for ten years. 

The solution is stable. 

The solution is scalable. 

We have an internal IT department that handles all support or technical issues. We are experts in our project tools so we smoothly solve all problems. 

We did not previously use another solution. 

We implemented the solution in-house. 

The solution is less expensive than other options. 

I recommend the solution and rate it a ten out of ten. 

We're using Microsoft Project on multiple tiers to perform inventory optimization, production planning, and purchasing.st built the project a week ago using Microsoft Project from start to finish. We built in all the functionality we have to cover. All the updates, action items, etc., are in there.

In my previous position with a leading 3PL, the provider of our warehouse management system, Blue Yonder, used Project. Nevertheless, it was seamless to integrate a Project file because Smartsheet offers the ability to upload MPP files. But at the same time, we would make changes and adjustments with Project. I'm currently using Microsoft Project for all my projects. 

Microsoft Project's integrated timeline is tied to the project plan almost seamlessly, and you add whatever action item or milestone you choose. All you have to do is set up a column and click on the timeline. It will automatically put it in there and allow you to choose the type, whether it's a bar or if it's a milestone, just pointing out that single milestone.

With Smartsheets, we can easily integrate and allow users outside the company to access our files. We can manage their access directly inside the project plan. I can allow my customers to jump on there to see the project while limiting their access to certain sheets or views. If I want I can allow them to view, edit, or share it. 

Microsoft Project has similar functionality, but I can't just give them a link. We have to bring them into using a company server because that's where we have it stored. There are more steps and assigning permissions is more convoluted.

The stability is generally good, but it's affected by the sharing aspect because you have to utilize OneDrive, Teams, or SharePoint. The stability is heavily tied to how quickly it saves the MPP file. If there's a processing gap when you're saving the project, it'll end up creating another edition. It typically uses your user ID  and tags it, but the original will still be there, and it may not have the changes. When you start to use it with additional users, the stability in terms of saving is reduced. It's maybe a five out of 10 for stability in that sense. 

Project is not as easy to scale. It isn't a cloud-based solution where everybody can utilize it at the same time without version issues when you save your file. We use it at the enterprise level, but you have to share the files with others within your organization through Teams or SharePoint. One improvement would be to transition to cloud-based functionality. However, that might limit the functionality in other ways. 

I haven't used Microsoft support for Project because I have enough experience that I don't need to. However, I have contacted Microsoft support recently to as questions about Excel. You can't pick up a phone and call them. Instead, you initiate a chat session on their website, and they will call you back in some cases.  

It may be because Smartsheets doesn't have the same global user base, but their problem-solving is fantastic, whereas Microsoft support seems a little convoluted.

The installation is easy. Setting up a project takes a little bit longer. It's not as intuitive as Smartsheets, but it's relatively easy. You have to have a base knowledge to use either product, but I would rate Smartsheets eight out of 10 for ease of use, while Microsoft Project is maybe five out of 10 because it's not as intuitive. 

It depends on the scale, but in some instances, the licensing was around $600 per user.

I rate Microsoft Project seven out of 10. 

I am using the Microsoft Project App in Teams and I use it mostly for project scheduling. We don't use it for reports or anything else.

Microsoft Project has helped improve my organization by providing transparency. Everyone can see what they're assigned and other information.

The most valuable features of Microsoft Project are the availability of being online and within Teams. My entire team can use it and see it, versus the full Microsoft Projects, such as Project Professional, you need to have a license.

All the versions of Microsoft Project could use improvement one way or another, but the specific version that I'm using, the reporting capabilities, and/or being able to link think other projects to it could improve. If I have a portfolio of projects that I'm working on, I want to be able to see a dashboard of all of my projects in one place. I haven't been able to do that in this particular version without using coding or PowerBI or anything similar.

In a future release, the dashboard should improve because there isn't one, I had to create my own.

I have been using Microsoft Project on and off for approximately 20 years.

The stability of the Microsoft Project is good.

We have not scaled Microsoft Project, it is only our 25-person IT departments using it. We have desktop analysts, project managers, and directors using the solution.

We do plan to roll out Microsoft Project to our business professionals on the business side of the organization, in the next three or four months.

We have not had any issues using the solution to contact the support from Microsoft.

We used LiquidPlanner previously. It was more of a time-keeping tool versus a project management tool. If I only want to build a schedule, I couldn't do that in LiquidPlanner without my team tracking their time.

LiquidPlanner is only good for timekeeping, and I couldn't get my staff to keep their time, it wasn't practical for us. I needed to be able to build a schedule and be able to track it on my own, versus what was done, versus people having to go in and track the time they work on a specific task. Whereas LiquidPlanner doesn't give me the opportunity to build a project plan without using timekeeping.

The initial setup of the Microsoft Project is straightforward. However, it was a Team's deployment and Microsoft Project is part of that suite. It took us approximately six months for the complete deployment.

We did use a consultant to help us deploy Teams and we were involved too. The consultant has been very helpful, we use them for all kinds of different deployments.

We have two systems analysts who are in charge of keeping Microsoft Teams up updated which includes Microsoft Project.  

We're managing projects a little bit better, we're a lot more transparent, and Microsoft Project is easier to report on, versus LiquidPlanner, which we spent a lot of money on. We saved all that money not having to use LiquidPlanner.

You only need a Team's license in order to use Microsoft Project within Teams, which is very helpful.

If an organization already has Teams, they already have access to Microsoft Projects, or at least Microsoft Project Online. There's no reason to buy separate project management software, at least for a smaller company like ours.

We did not evaluate other options. We used what we had, and tried to save money. We already have Microsoft Project, and we decided to use it.

My advice to others would be to do extensive training and tutorials and create QRGs. It's new and not a lot of people know how to use it. Training is the most important.

I rate Microsoft Project an eight out of ten.

We primarily use the solution for portfolio management, project management, and program management. It is also used for reporting to leadership on a portfolio level.

It gives the enterprise and leadership the visibility of what's going on with their enterprise. It provides visibility to all the projects that are going on within the company.

The integration between SharePoint and Power BI has been great.

The stability is good.

You can scale the solution as needed. 

We need more integration with Microsoft Teams and other collaboration tools.

The product could be more user-friendly in some areas. 

I've used the solution for a while. I've used it over the last 12 months at least. 

The stability is pretty good. It's easy to use and reliable. 

The solution can scale. It can scale for a company that's dealing with a medium-size company dealing with 10 to 20 projects, all the way to the large companies dealing with hundreds of projects it's very scalable.

We've got the technology department using the product. We also have businesses using it as well. We have a total of 100 plus people that are using it today in our company.

The solution is being used extensively. We do have plans on working with a third party to potentially make the solution even more user-friendly.

I haven't used their technical support, however, I've partnered up with Microsoft Partners to come up with potential future solutions.

Before Microsoft Project Online, we just used Microsoft Project Desktop and we utilized Microsoft SharePoint to create lists in order to create portfolio trackers and project trackers that way. We needed a more robust solution that can track risk management, budgetary prioritization, et cetera. Microsoft Project does that for us.

The setup can be both complex and easy. I'd rate it 3.5 out of five, with five being an easy setup.

Deployment involves usually implementing the new tools and then adopting and having people use it. Implementation took about three months and then the adoption took another six to eight to nine months of training and making sure people use the tool.

We have admins and that's one or two folks that can handle any maintenance requirements. It's not a high-maintenance product.

We had a consultant assist us with the implementation.

We've seen an ROI from the aspect of efficiencies and having information in one central location. We've cut time in reporting. We've cut time in the administration portion as well, of setting up projects so there's been efficiency. We hope the ROI might expand as we use it more.

I'm not aware of what the licensing costs are. There might be extra costs associated with maintenance. 

While it is my understanding that we did look at other solutions, I was not part of that tendering process. I don't know which ones were vetted.

We're a customer and end-user.

I'd advise potential new users to make sure they select a tool that will be useful to the end-user. This tool is really catered to project managers, while the majority of the folks who are executing projects are not what I call professional project managers.

I'd rate the solution eight out of ten.

We use Microsoft Project for creating the implementation projects for IT, such as anything from infrastructure through application deployments. In the current project, we are using it for the cybersecurity measures that we're implementing.

Microsoft Project has helped our organization by tracking the capabilities of when we can deliver a solution.

The most valuable features of Microsoft Project are you can create critical paths pretty easily, and you can import from an Excel spreadsheet to your task list as you create it during your working sessions with your team.

Microsoft Project could improve the interface, it should be more intuitive. It could be adjusted a little bit to make it a little easier to use and more user-friendly. It is a very powerful tool and it takes people a while to get used to it.

I have found that when you're saving your project plans to a SharePoint site it does not work well. I am not able to check it out and check it in as I would on the Microsoft Project's server. If you have multiple people trying to edit tasks in the project plan for the completion or status, it doesn't give you abilities to check the project in and out. It limits who makes changes to a project plan if multiple people are trying to do it at the same time. You can potentially overwrite someone else saved changes. There is not a lock on changes to the project plan. If I'm trying to change something, it's whoever saves first, then the changes go in. If you're working and extensively updating a lot of things in the project plan, then somebody else comes in and updates one line, they could potentially override everything that you've changed.

There are some accessibility issues that could be fixed. 

I have been using Microsoft Project for approximately 15 years.

Microsoft Project is scalable. I've used it in the server mode where I ran multiple projects under a program, which were very large project plans with up to 1,000 lines, and I didn't have any problems with performance or managing projects.

We have approximately 1,000 users using this solution in my organization. They are typically project managers. 

We are using Microsoft Project extensively on some projects. However, it depends on the type of project, it doesn't lend itself well to non Waterfall type activities.

I have not contacted the technical support.

Our IT department handles the deployment of the solution. I can tweak it on a per-project basis. However, the implementation or installation of the software is done quickly.

My organization is pushing to move to the Jira platform or to use Scrum instead of Waterfall.

I would recommend others to buy a Microsoft Project book that has tips, and a lot of them have templates for different types of projects.

I rate Microsoft Project a nine out of ten.

I use the solution for scheduling and planning.

The solution helps us stay on track with our project and insures we meet our deliverables and requirements.

The reporting and national resource capacity planning are the most valuable features.

The collaboration has room for improvement.

I would like to request the addition of risk management and financial management to the solution.

The cost has room for improvement.

The initial setup has room for improvement.

I have been using the solution for ten years.

I give the scalability an eight.

The initial setup is complex.

The solution is expensive.

I give the solution an eight out of ten.

I recommend the solution.