Microsoft Project Reviews

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.

I primarily use the solution for project planning. 

The product is very easy to use. It makes it easy to present projects as well. 

It's an easy solution to set up.

The solution can scale.

It is stable.

We'd like the solution to have better integration with other third-party and open-source solutions. We have trouble importing and exporting to other tools. 

I've been using the solution for two to five years. 

It's a stable solution. It's reliable. We haven't had any problems with it. There are no bugs or glitches, and it doesn't crash or freeze.

The solution scales well. It is very easy to extend it. 

We have about five to ten users on the solution. At this point, we do not have plans to increase usage. We might in the future. 

I have not used technical support. I've never needed assistance. 

I have used a different solution previously.

The initial setup is very simple and straightforward. 

It is quick to set up. It took about an hour to deploy.

We have five people that are able to handle deployment and maintenance tasks. Typically, we have two or three available. 

We handled the deployment in-house. We did not need any outside assistance. 

We pay a monthly licensing fee for the solution. I'm not sure of the exact cost of the product.

I am not sure if we are using the latest version of the solution. 

I'd recommend the solution to others. 

I would rate it eight out of ten. 

I am a project manager, so my primary use cases for Microsoft Project are the creation of a work breakdown structure – the time and schedule of the project – and following up on it. I also create reports. We're not using the enterprise solution and are not connected to a PMO. 

The features I find the most valuable are scheduling and reporting. I mostly do short projects that last three to six months. These are simple projects with a limited team of three to five members. We do not even do updates through the application. We do updates through meetings. 

The tool currently has a limited number of tutorials now. Those could improve, which would be helpful. 

They could also work on integrations with solutions like Teams. We have all of our project files in Teams and it is much easier to use for communication than MS Project, but there is no integration of the two solutions. 

I have been using Microsoft Project for about three years.

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

My impression is that scalability is quite good for more complex projects.

We are in a good partnership with their support team. We have an account manager and we have a support team. They're very supportive.

Positive

I tried to use Primavera, but I didn't find it as easy to operate in as MS Project. However, that was an older version. I don't know if they have updated or simplified the application.

I would rate the initial setup of this solution an eight, on a scale from one to 10, with one being the worst and 10 being the best. It's not very complicated. Even if you download and use the application for the first time, you can easily find your way.

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

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.

We primarily use the solution for managing projects. 

The ability to create tasks and structure them and give them hierarchy. 

They now have MS project Online and they have two levels, so it's easier to access what you need and to choose specifically what you'll use. You can start at a lower level, for example, and be more cost-effective and move up if it suits you.

It's easy to set up.

I don't have any comments on where it can be improved. 

The full suite would be pretty expensive.

I've used the solution for many years. 

The stability is good. There are no bugs or glitches. It doesn't crash or freeze.

The solution scales well. It's not an issue. 

We're a small organization with a few people using it. 

The solution is simple to set up. It's not overly complex. Especially now, after working with it for so many years, it's very easy.

It's an online tool. From that perspective, there is no maintenance needed.

The pricing is good. You can start at a lower tier and move up as needed. It's reasonably priced to start.

I cannot recall the exact costs. It's comparable to other similar products. 

It would be more expensive all in all as some of the competitors will have more features and other bells and whistles that would not be available with the basic tool of Microsoft, which would be cheaper. If you want a full suite, it will be more expensive.

I'm just a customer and end user.

It would be a straightforward option for people who are already using the Microsoft suite, including Office 365. If you're not a Microsoft shop, it's probably not your tool.

I'd rate the solution seven out of ten based on the cost and features on offer. 

It is easy to define timelines with Microsoft Project. You can get a clear picture of the model, you want to create.  You can create inside an agile or waterfall model. Microsoft Project is easy to delegate tasks to different members where you want to put the task and who you want to work on it so that you have a clear path.

Right now you can create a timeline with the major up tasks, but there's no real way to mark it. When you are planning, you usually have resources on board for a single task.  Microsoft Project has no way to mark it because it is based more on agile methodology. Many times you want to take it by the resource count and that is where it becomes tricky. 

 I would like to see an entire baseline, like in JIRA. It is like project planning in JIRA, but there's a whole story building that you can do. Microsoft Project needs to incorporate some points of story-building and epic building, which are currently missing. 

I have been working with Microsoft Project for the past month.

Microsoft Project is a stable solution.

There is no problem with Microsoft Project's scalability.

I do not use Microsoft technical support because our company has its own technical support team.

I only use a login feature for Microsoft Project. 

I would rate Microsoft Project an eight and a half 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.

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.