Microsoft Project Reviews

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.

We are doing e-commerce implementations and we organize the projects and Gantt charts for this task.

It's great for project planning and monitoring.

It's very easy to use. It's plug-and-play. 

The solution is stable.

It can scale well.

The UI is great. If you work with Microsoft, it's very easy to work with this.

It can be hard to create things manually, however, once we have it up and running it's very easy.

We'd like to have more resource allocation and monitoring features. This should be part of MS Project. 

We've been using the solution for almost a year. 

The stability is good. I'd rate it 8.5 to nine out of ten. It is reliable. There are no bugs or glitches. 

The solution is scalable. We just give the order to the reseller and they activate more licenses.

We have 60 to 70 users. We do have plans to increase to 200 licenses. 

We have a reseller partner that offers technical support for any tickets logged. 

The setup is based on the business requirements. It's not too difficult. 

The deployment takes four to six weeks.

We activated the license and then, to use MS Project, we have to create a whole project plan, and that requires manual data entry. Then, once we have that, everything moves quickly.

We do not need any technical people to maintain the product. It's very user-friendly and maintenance is very minimal. 

This is a cost-0effective project planner. I'm getting a product at $100 as opposed to Oracle, which would cost me thousands of dollars. I'd rate it nine out of ten. 

We pay annually. You can also pay monthly if you would like.

There are no extra costs in addition to the standard licensing fees. You would have to pay if you were using other Microsoft products, like Microsoft Teams. 

We did evaluate OIracle and found the price to be too high. The implementation timeline was also very long. 

We're using the cloud-based solution so were are always on the latest version. 

This is a Microsoft product and therefore it is very user-friendly. We use a lot of Microsoft products and find it very simple to get used to the UI since we use so much Microsoft in general. 

I'd rate the solution eight 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 product for Excel and other processes. 

We value all the features. Previously, we used Jenkins for similar purposes, but Microsoft Projects works fine. We're looking to improve integration with different clusters on production and automate various aspects of software development. This includes integration for alerting, monitoring, and pricing purposes, among other things.

The tool's deployment is complex. Integration and automation also need to be improved. 

I have been using the product for ten years. 

We're exploring various options to improve stability. Currently, it's a bit tricky, but we're working on making it more stable.

We're making every effort to enhance scalability according to our business requirements. My company has 5000 users for Microsoft Project. 

Our deployment process follows standard procedures, often dictated by project requirements. We allocate two personnel for installation and project requirements. Currently, we have nine to ten projects.

We use Microsoft Teams for business communication and file sharing. We've also integrated Microsoft Teams with Grafana for on-call support and Jira. In our project work, we utilize Jira, while for resource management, we rely on Salesforce. I rate the overall solution a seven out of ten.

Occasionally, we have encountered issues that would require us to restart the solution. I recommend getting familiar with the documentation and thoroughly testing the product. Additionally, it's essential to connect with different stakeholders to address any issues.

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 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.

We primarily use the solution for project management. For example, IT implementation projects. 

The Gantt chart view is great. It shows all activities, and the planning of durations is very easy. We can see our suppliers and everything. 

The solution is stable.

It's scalable.

It doesn't really work too well on a Mac.

The initial setup was a bit complex. I find the setup a little bit cumbersome. Sometimes there are certain rules that automatically update something else, and it's not always visible. When that happens, you are left with a surprise.

I've used the solution for six years. 

The solution seems to be stable. There are no bugs or glitches. It doesn't crash or freeze. 

With some assistance, it is possible to scale the product.

We have around 1,000 people using it in our company.

I have not used technical support and therefore cannot speak to how helpful or responsive they would be if you needed help.

I have used other products in the past.

The initial setup was a bit complex. It wasn't overly simple. 

The licensing is handled centrally within the company. I don't have any visibility on the pricing aspect. I can't say how much it costs our organization precisely.

I have evaluated other products. 

I'm not sure which version of the solution we're using. I don't know the version number off-hand. 

I'd recommend the solution. I find it to be quite useful, especially for waterfall-type projects.

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