Microsoft Project Reviews

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. 

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.

Microsoft Project is one of the main tools our teams abroad use for planning, and it's very flexible. Local teams use it to manage small projects locally. It's also a repository for storing financial information that we don't want to track down. 

Teams use Microsoft Project for tracking tasks, managing requests, assigning resources, and following up. Workers can submit work to managers for approval and then it's submitted to the main process. 

Microsoft Project provides a starter tool that project managers can learn before moving on to solutions that are more convenient or widely used in the company. The interface is intuitive, so anyone can jump in and start planning. 

It's also a tool that is common among many companies, so if I take a new job at another firm, there's a good chance they will be using Microsoft Project, too. When we hire a new person, they can usually start working right away without any training. We only need to teach them how to apply that knowledge to the other tools we use.

Microsoft Project integrates well with the Microsoft Office family of applications. It has plugins that interact with it and you can use it with Microsoft Teams. We can use plugins to communicate with JIRA, Projectplace, and Planview. It's not widely used in the company, of course, but it's something that can interact with the official tools that we have. 

You can do a lot of stuff with Microsoft Project, but the licensing is for individual computers, so it's not connected to a central platform like the one that we have in Planview. 

Planview FLEX licensing gives us a central repository where all the projects are stored so you can check the finances, resources, etc. It's quite useful to have everything connected. We don't have that for Microsoft Project. It's disconnected. The reporting capabilities could also be better, especially with finance and resources. Everybody complains about reports. That's why we need another tool. 

I've only been using Microsoft Project for a year. I have more experience with Planview Projectplace, but we use this as well. I'm primarily responsible for Projectplace in my role. I do onboarding for other teams, create the workflows, and work with use case scenarios for various teams worldwide. 

It's an on-premise solution. It's never going to break down because it's installed on a local computer. It's highly stable from that point of view, but our use case is also limited. 

A project management application is only as powerful as the information you put inside. Projectplace is available to time reporters, developers, engineers, resource managers, and financial controllers. It is a powerful tool that provides a centralized way to gather information. 

A director can access Projectplace and see every project involving their teams. You can create custom reports. We have teams that design new reports for the various needs we have. That's the most powerful feature a project management solution can have—the ability to pull out information. That's something we don't have with Microsoft Project.

I rate Microsoft Project seven out of 10. Better tools are available. Microsoft Project is a decent tool for small startups and medium-sized projects, and it's widely used. 

We work with customers to develop products from scratch. The process involves multiple design teams, financial controls, and planning. Each project is part of a larger program, and we have to follow up on that. There are tons of tools that can do this way better. Microsoft Project, in my opinion, is for small and medium-sized projects.

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.

Microsoft Project is one of the only solutions you can use in just about any industry. It's difficult to do that with most other project management tools. There is a lot of flexibility within the product assets. Most sectors can utilize Microsoft Project successfully because it doesn't have any generic adapters. Primavera is a competitor from Oracle, and they've got adapters for some industries but not others. For example, they have adapters for construction management, so people who are on construction projects usually go for Primavera because the adapters make it easy for them to scale out a project.

With Microsoft Project, you need to do more work to get the same thing, but that is the advantage of having adapters. Adapters make it easy for certain sectors to implement their projects, but Project doesn't have that, so anybody can use it. That is the best thing about Microsoft Project

Microsoft Project has much room for improvement. The solution is still stuck where it was in 2013. Not much has changed since then. There is a lot that can be changed in the enterprise segment.

There hasn't been a significant addition to the enterprise part of Microsoft Project since 2013. The biggest change was the integration of Power BI reporting into Microsoft Project. Other than that, we are seeing still the same features 

Some of the underlying things have changed. For example, data management is quite different. It's called Dataworks, and database management is different. Data is handled differently, but there haven't been any new features on an enterprise scale. 

Microsoft has developed more user-friendly Project implementations beyond enterprise use cases. They're transitioning from the enterprise platform to something that everybody can use, but they are losing out on features.

We have been selling Microsoft Project for a couple of years.

Microsoft Project is stable, but it requires a lot of customization. 

Microsoft Project is highly scalable. It can handle anything from one user to 10,000. What makes Microsoft Project different is that a single person can handle thousands of tasks in a project easily.

We haven't spoken to anybody at Microsoft support because they do not have a big team on Microsoft Project for this region, but we learned about production solutions through implementation. 

We picked up a couple of orders for Microsoft Project for certain shipbuilding companies. We took their projects and did a study, then implemented a solution for them that was tailored to their particular needs. We learned on the job, but there was no guidance or support from the vendor.

Project is essentially an extension of an Excel sheet. You need to configure a lot of things to get your project management done correctly, and the use case scenario is different for each customer. Some require Project for certain needs, which may not be the same for the next customer. We need to understand the customer's work requirements, and we will build a solution on Microsoft Project.

Seven out of 10. My advice for Microsoft Project or any project management solution is to set clear goals. You need to have a vision in mind when thinking about Microsoft Project deliveries or any other project team delivery. If you don't have a clear vision, you may not realize project value, and that might lead to issues.

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.

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.