Microsoft Project Reviews

I'm using it to prepare a project schedule, budget the project, and handle resource allocation. I'm checking on if the resources or the tasks are completed and if they're on time and to see if I have any backlogs with tasks.

I'm using it just for my academics, and it does the job as far as I'm concerned for this use case. We are just using what is relevant to the course, and that's it.

The setup is straightforward.

Once you understand the solution a bit, it becomes easy to work with.

The solution is stable.

It can scale. 

It has a bit of a learning curve since there are a lot of features in it, and we haven't really gotten a chance to train through the whole product.

I've used the solution for just two months. 

It is quite stable. There's no huge amount of data that is being used on it and even the simplest of computers can use it. It doesn't consume much data. There are no bugs or glitches and it doesn't crash or freeze. 

Scalability isn't a problem with Microsoft Project. It's just a scheduling tool and the only people who will be using this tool will be the managers, and there are not many managers. There's not much data processing on it.

You can share the dashboard too, so the number of users doesn't really matter. You create a project and you schedule it. You can share it with others and scalability is not an issue.

I've never dealt with technical support. My college provided me with the solution, and I haven't had to troubleshoot anything. 

The initial setup is straightforward. You download, install, and use the product, and you get set up your projects. That's it.

I'm using the solution for free via my college. I can't speak to the pricing or aspects of the licensing. 

I haven't used it extensively. If I had used it in the environment where I was working, and I was responsible for the task I was doing, I would've experimented more on it and figured out something. However, that's not the case.

We are aware of how to install certain processes exactly and how to use those processes in Microsoft Project. However, you'll have to spend at least a week or two days at minimum to see how everything works and what kind of allocation works best. There are a few things that you need to be specific about. With Microsoft Project, it becomes easy to use when you know what you're doing.

Using the product will not be a big challenge if you are comfortable with project management. 

I'd rate the solution nine out of ten as it was easy to learn and a very useful tool in general. 

The solution allows users to manage projects and project portfolios. 

The solution makes it very easy to plan and has great customization capabilities. 

The setup is very simple and straightforward. 

It is stable.

It's a scalable product, especially the online version. 

There's a lot of great documentation available online. Users can teach themselves to use the product.

It would be ideal if the solution integrated more with  Azure DevOps and other work management platforms like Jira.

I've used the desktop and cloud version for about three or four years.

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

The online version of the solution is quite scalable. The desktop version is just for one user.

The number of users varies according to the project. On one, we had maybe 40 users, on another, we had 500.

It is being used quite extensively at this time. We do plan to increase usage.

We've never reached out to technical support in the past. I can't speak to how helpful they are. 

It's easy to set up the solution. It's not a complex process. 

We only need one person to deploy and maintain the product. They are an admin.

We did the setup in-house in one day. We did not need outside assistance. 

The solution is part of Office 365, and it is an annual subscription.

We can use the solution on-premises and on the cloud. 

I'd rate the solution nine out of ten.

I'd recommend potential new users seek out videos and documentation to help learn the solution. There's a lot of good content that is very helpful to new users, and a lot of it is free. 

I primarily use the solution on my desktop for my personal needs.

It is very easy to deploy. 

The solution is stable. 

Microsoft offers good support.

I'd like the solution to be less expensive. 

It's a Microsoft product and therefore it is stable. The performance is good. There are no bugs or glitches, and it doesn't crash or freeze. 

I cannot say that it's scalable. It's on MS sources, so it's on the desktop. We don't really scale the product.

I haven't really relied too much on technical support, however, they are good.

Positive

I did not previously use a different solution.

The solution is very straightforward and simple. It's not as complex. You can connect the license in less than 30 minutes on a desktop.

I handled the initial setup by myself. I did not need the help of outside resources such as consultants or integrators. 

The licensing costs vary. It's largely very expensive. 

I'd recommend the solution to other users and companies. 

I would rate the solution nine out of ten.

The most valuable feature of Microsoft Project is scheduling. The solution is useful on a daily basis.

Microsoft Project could improve the dates. Sometimes the dates are not aligned. This occurs even when you auto-schedule the dates. We have to go and define the schedule daily this should more easily accessible.

I have been using Microsoft Project for approximately 10 years.

Microsoft Project is stable.

The scalabiltiy of Microsoft Project is good.

We have three or four people using this solution in my department.

I have not used the support from Microsoft Project.

I have not used another solution prior to Microsoft Project.

I rate Microsoft Project a nine out of ten.

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's my day-to-day software.

I use it for my projects. I handle the portfolio. I have multiple projects and I need to monitor those projects and generate reports and consolidate everything.

The functionality is great. 

Microsoft Project is good overall. However, I especially like the reporting tools, which are visual tools and offer visual reports. The visual reports is what I like about Microsoft Projects.

The initial setup is straightforward. 

The Gantt set needs to be improved. The grid lines needs to be more interactive.

The Cloud version has far more advanced features in it. I haven't hands on it yet, however, I have seen the product, and it has all the enhancements that are required.

I've been using the solution for 15 years now. 

It is a stable, reliable solution. There are no bugs or glitches. It doesn't crash or freeze. 

We have about 100 people on the solution. 

The company is now starting to use the cloud version. They stopped implementing any other versions. Once we migrate to the Cloud version, then we have to see how it's going to compliment us in terms of scaling.

I've not contacted the call center or the support center for any support. I go on the community website and try to find it to see if I can find any kind of troubleshooting steps there, and I manage issues on my own.

I used Primavera previously. 

Primavera is not user friendly, and has no support on the database types. It requires certain a format to be implemented. There are many differences between these two solutions. For a billing or for operational use, Primavera definitely doesn't really suffice.

The setup was straightforward and not as complex as Primavera or any other project management tool.

When it comes to the on-prem deployment of the older versions, you don't usually get the results, you don't find it online. They are not readily available. We need to get into the third party applications and download the third party results. From there on, it's a marathon to install. The cloud version is easier. 

There's not really any maintenance needed. 

I used my administrator during the implementation. I asked him to assist me.

I don't have very much information in terms of pricing. However, it is a necessary tool for us and therefore whether it's cheap or expensive for us.

I'm not sure as to if we need to pay for any extras or deal with ancillary fees. 

We are partners with Microsoft. 

I'm working with the 2019 version at this point. 

I'd advise users to go for the cloud version. It's easier to deploy and share. 

I would rate the solution seven out of ten. 

We are in presales, and when the planning is very complex, we use Microsoft Project. That is, when we receive an RFP, we propose our solution and plan and build the different processes in Microsoft Project.

I like that I can change the task and include different resources related to the task.

It would be better if Microsoft Project were included in the DevOps stack. That is, I'd like to see this tool integrated to a different stack of the applications that we normally use in DevOps, such as in Jira, for example, to deploy a different version related to the different tasks that are included in Microsoft Project.

I've been using this solution for more than 10 years.

My impression is that it is stable.

It's very easy to install and use. It doesn't take a long time to deploy.

We have about 1000 people using it in our operations department.

I recommend using this solution if you working on a complex project or complex system.

We use Microsoft Project to plan our projects, including some tasks that we need to accomplish. We use JIRA as well. We use a lot of tools to plan our jobs.

The user interface is simple and it helps me in planning what needs to be accomplished.

I am a regular user and for me, it is perfect. I would love to see a mind map feature where you can draw some diagrams of the project. Then you can connect ideas and watch them on a map.

I have been using Microsoft Project for more than five years.

We use a cloud solution and it is transparent for us. We have the perfect client and it saves the data.

I have no idea about the cost because it is a corporate decision. 

I would rate Microsoft Project a nine 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.