Microsoft Project Reviews

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.

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. 

I use the solution in my company for our one project involving some product implementation, so it was used from the project's first meeting to the delivery phase.

Tracking timeline, resource allocation, and monitoring are areas of concern for the tool where improvements are required. Improvement in tracking timelines, resource allocation, and monitoring can help our company check whether each and every activity related to a project is completed or not. If the company notices any issues in the timeline, then we can reassign such tasks. The product should allow our company to collaborate with Microsoft Teams so that our company can complete a project within the set timeline.

I have been using Microsoft Project for 3 years.

The product offers good stability. Microsoft products usually offer a certain level of stability to users.

It is a scalable solution.

My company has three users of the product.

As of now, there are only three users of the product if I consider the project my company has been handling.

In the past, my company used to use Microsoft Excel to track some project-related activities.

The product's initial setup phase is easy.

The deployment is not at all complicated since our company only had to download the product from the solution's official website, after which we enabled the licenses to use it.

The product helps its users save the time attached to the manpower required. In the product, users can fix the delivery time and fulfill their project-related commitments to their customers.

The product is not expensive. My company has opted for an annual subscription.

Microsoft Project's integration with the overall project management processes in our company has been possible through Microsoft Teams which was used for meetings and it was also used to assign and set goals, priorities and timeline.

While handling the project in the company, Microsoft Project improved team collaboration since the tool could provide reminders based on the timeline. The tool helps to keep a check on whether the teams in our company are going through their daily work and completing the project within the committed time as per the schedule.

The most beneficial part of the product in terms of tracking project progress stems from the fact that it provides users the ability to easily track each and every activity concerning the project.

Speaking about the impact of resource management features in project planning, I would say that in the beginning of the project itself, my company had allocated the resources and had set the goals along with the timeline. With the tool, it is easy to monitor the daily activities of the project.

Speaking about how the reporting functionality in the product helped me with the decision-making part, I see that the product allowed me to collaborate with Microsoft Teams.

I recommend the product to others who plan to use it since it allows its users to easily handle projects, allocate resources, fix the timeline, and track and monitor the progress of the projects. It also helps its users to assign tasks to others.

I have not faced any challenges with the product's scalability and integration capabilities.

I rate the tool a nine out of ten.

We use it for the Gantt functionality. We can do project schedules and use the WBS piece to break down the work. We are able to generate reports for leadership to show project schedules, milestone schedules, etc.

It is installed on the desktop. It is not connected to the project server or anything like that. 

Being able to get a milestone schedule or a breakdown out of it is valuable. It can integrate into Visio, which is helpful.

Its user interface could be a little bit more intuitive. Not everybody has the luxury of going to training and understanding which button does what and the functionality. The user interface should be improved to make it a little bit more intuitive. It is not user-friendly. I've dealt with it for a number of years, so it is not hard for me to figure it out, but you would need a quick reference guide or something to say, "Here are the basics. This is how you do X."

I have been using this solution for about five or six years.

It is stable.

I haven't contacted them.

It takes a while to build, but it will probably depend on the project size and all the dependencies. So, it isn't exactly straightforward, but it also depends on the size of the project or the scope of the project.

It is pretty straightforward. There isn't anything heavy about it.

I would rate it an eight 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.