Microsoft Project Reviews

We use Microsoft Project for any project executions, like assigning the resource, listing out the task, and following up on the timeline. Microsoft Project is used to track the project delivery and the project management.

It would be better if the solution is integrated with other communication platforms like Microsoft Teams. Microsoft Project has a separate license from Microsoft 365 and has not collaborated with Microsoft Teams.

I have been using Microsoft Project for five to six years.

Microsoft Project is a stable solution.

Around 30 users are using the solution in our organization.

The solution’s initial setup is straightforward.

We implemented the solution through an in-house team in one month.

We have seen a return on investment with Microsoft Project because it allows us to track and execute the project successfully without much delay. Since projects are executed on time, it's always beneficial to our business.

The solution has a decent annual license subscription cost, which is not high.

I would recommend Microsoft Project to other users. As an end user, Microsoft Project provides many features like tracking the team task, checking whether the task has been completed on time or there is any delay, tracking each task, and resource allocation.

Overall, I rate Microsoft Project an eight out of ten.

The primary use case of this solution is to help plan the work and implementation plans for our projects.

I find all the features of the solution valuable.

The solution is currently a bit slow and can be faster.

I have been using the solution for one year.

The solution is stable.

The solution is scalable.

Before switching to this solution I used online tools to help with our project implementations and monitoring tasks.

I believe the licensing for the solution is based on an annual fee.

I give the solution an eight out of ten.

We have over ten people in our IT project department that currently use this solution.

I recommend the solution to everyone.

The most useful feature is to link sub-tasks to the main group.

The setup is pretty simple. 

It is stable, and the performance is good.

It can scale well. 

What could have been better is the integration with Office 365 so that if you're discussing a project on Teams or there's an email related to the project, it can be tagged to the project in Microsoft Project. That functionality is currently not there.

The solution is pretty expensive. However, you pay for what you get, and it is worth the cost.

I've been working with the solution for more than ten years now. 

It is stable and reliable. There are no bugs or glitches. The performance is good. It doesn't crash or freeze. 

The solution is absolutely scalable. It's not a problem to expand the product. 

We are a small consulting firm. We have only four users at the moment.

I've had no issues with the level of service provided by support. They are helpful and responsive. We always get an immediate response. 

Positive

We have worked with Jira.

We always knew that Microsoft Project is the most comprehensive option. Although our clients are using multiple different platforms, we tend to integrate all those outputs into our Microsoft Project installation.

The product has a simple, straightforward implementation process. It's not overly complex. 

The pricing is pretty high. I'd rate it two out of five in terms of affordability. 

We are customers and end-users. 

I'd rate the solution seven out of ten. 

I would recommend it for companies that have a large number of projects and diversified teams. When I say diversified teams, I mean geographically spread and working on multiple projects. Those are the kind of people who could make use of Microsoft Project very well.

My primary use case is mainly to get down on paper the steps for our project - including who's responsible for them. We use it as a communication tool and then we (on a regular basis) review progress against the laid-out project plan or schedule.

I tend to step in and create schedules when project managers are too busy or oftentimes I'll create the initial schedule due to the fact that I know all the stuff that needs to go in it, and the project manager may or may not know that.

The solution is very useful for project planning.

The solution is extremely stable.

The solution can handle large-scale projects.

I'm totally confident that somebody that uses it more frequently and more deeply than I do certainly is aware of the features and functions in it that I just don't use. It's user-friendly, rudimentarily. I'm just creating tasks, linking tasks in terms of predecessors and successors, adding duration to the task, adding resources to the tasks, and coming up with the logical flow and the end dates. That's how I use it. And, in that sense, it's very easy to use.

One of the things that we struggle with is that we do a lot of smaller projects that end up using the same resources. We have difficulty managing or balancing workload across resources that are on multiple projects. 

For example, in project A we'll schedule Joel to do something in a certain timeframe. And then next day we have project B's schedule up, and he's scheduled to do something on that project in the same timeframe, and we don't have a way to expose those conflicts. We have to basically rely on Joe to say, "Hey, you've asked me to do different things. There's only one of me. I've got to manage my time. Either you give me twice as long to do both of those things, or you tell me which one to do first, and then move the other one."

It would be ideal if the solution itself could expose such conflicts.

One of the reasons that we have some projects using Jira as well as Microsoft Project is that we have to be able to access the project schedule to see, as an individual contributor, what the tasks are. It's not a great way to distribute that. In terms of Jira, where we create the Jira records, an engineer can go into the Jira database and search for his or her name, find all the tasks with the due dates on them, and anything assigned to them. If Project had a better mechanism to allow those who are not the project manager to see their own work tasks, that would be of help or of value to us.

I dabble in the product. We have actual project planners that are the experts in it, however, I've been using it for seven years at this point. It's been a while.

The solution is extremely stable. It's rock solid. I've never had a problem with not working. There are no bugs or glitches. It doesn't crash or freeze.

Some people in our organization do keep super detailed, large project schedules in Microsoft Project. I'm not working on such a large project at the moment. I'm working on many small ones. I can't comment from direct experience, however, I'm confident that we are doing that within our organization and that it can scale to handle quite sizable projects.

I've never dealt with technical support. I cannot speak to how helpful or responsive they are when they receive queries.

I do not recall the company using a different solution. Certainly, when I started in the organization, I was using this product and not something else.

That said, we do have some projects using Jira as an agile approach to project management. With Jira, what they'll do is we'll have a project schedule, and then they'll break down the individual line items on the project schedule even further into Jira tasks in two-week bites. That's how they're managing projects there. 

I did not handle the initial setup. Our IT team handled that part of the process for the company. I just open it up and create a new project schedule. Therefore, I cannot speak to how difficult or straightforward the process is.

Our IT team did the initial setup.

I don't deal directly with sales or licensing. I can't speak to the exact cost or licensing structure of the product itself. It's not an aspect I deal with directly.

We likely have a support contract for the product.

We are customers and end-users.

I'm not sure which version of the solution I use. I don't use any advanced features. I basically put in tasks and assign resources, and assign predecessors, and successors. That's about the level I use it at. I don't do tons of work resource balancing, or Gantt charts out of it or anything like that.

I would rate the solution at an eight out of ten. It more than meets my needs for what I'm using it for. What a real project manager may rate it might be different.

We primarily use the solution to enter our status and our time. For each task that we're doing, we have to enter a monthly status. It's for project management.

Overall, the solution has been so much better than the previous project management tool we had been using.

It's very easy to select the projects. It's so easy to save the project, task, and hours that I want. You don't have to think about it. 

The user interface is so clean. The previous EPM product was so hard to understand in terms of the user interface.

Once we commit our status, changing it is hard. Sometimes, I may make a mistake about a holiday or something. I may not remember that there was a particular day that was a holiday and I may enter time on that day as if I worked. Sometimes I want to fix it. It would be ideal if the holidays were pre-installed so that we wouldn't make that mistake, that would be ideal. It should allow us to set it so that we cant enter time on holidays. 

I have only explored maybe 5% of Microsoft Project as we're only using it to log things. I haven't seen a lack of features.

I've been using the solution for about one year at this point.

I haven't had any issues with stability. There aren't bugs or glitches, at least, none that I have witnessed. It doesn't crash or freeze. Overall, it's quite good.

Every employee has to use this solution, and we are a sizable organization. Likely, we have thousands of users on this product.

The solution is on the cloud, and therefore it can scale so well. We have our own internal cloud, and Microsoft has a cloud as well. If a company wants to expand it, it should be able to do so with relative ease.

I can't speak to the quality of Microsoft's technical support. I've never contacted them, so I can't say how knowledgeable or responsive they are. We have our own internal support. We are a very big organization, so we have an internal support team that assists us if we need help. They may reach out to Microsoft directly, however, I have no knowledge of their interactions.

We did previously use a different project management solution. I've only seen the user interface. It's my understanding that it is called EPM, or something to that effect. I like Microsoft's solution much more. It's a better product.

I only use the solution. I did not have to set it up. I can't speak to how easy or difficult it is to do this as I am just an end-user in the company.

I'm an end-user and customer. My organization is a large company and we're a big customer of Microsoft.

I don't know which version of the solution I'm currently using.

My life has improved so much with Microsoft Project. It works extraordinarily well.

Overall, I would rate it at a nine out of ten.

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.

I use Microsoft Project to manage project timelines.

Microsoft Project should provide better documentation regarding the usage of the solution.

I have been using Microsoft Project for the past five years.

Microsoft Project is a pretty stable solution.

I rate Microsoft Project an eight out of ten for stability.

It depends on your system's RAM, but Microsoft Project is scalable. Three users use the solution in our organization.

I rate Microsoft Project an eight out of ten for scalability.

I previously used the solution called Trello.

Microsoft Project's initial setup is straightforward.

Microsoft Project was deployed by the IT team and my office administrator within thirty minutes. You can just install the solution and start using it.

The ROI with Microsoft Project is good as there's a real need for the solution.

We have to pay for a yearly license for Microsoft Project.

I would recommend Microsoft Project to other users and ask them to get trained to use the solution.

Overall, I rate Microsoft Project an eight out of ten.

We use Microsoft Project in a fairly run-of-the-mill way. Our primary use case for this solution is project management.  

What I find the most valuable about Microsoft Project is the fact that nearly everyone is familiar with it and understands how to use it. This enables us to use the tool with different customers or partners.

I would like to see more integrations with another software tool. The market is more collaborative now, so it is always good to be able to share information between different tools. If a client does not have Microsoft Project, they probably have another one that the solution should have an integration with. 

I have you been working with Microsoft Project for at least 25 years now.

Microsoft Project is really stable. It has been stable for us for years. 

I think Microsoft Project is a scalable solution. 

We have not had any problems with Microsoft's technical support. We are happy with the support. 

We are paying for a yearly license. On a scale of one to 10, with one being cheap and 10 being expensive, I would rate Microsoft Project a nine. 

Microsoft Project is a good tool. It is very easy to integrate and set up.