Microsoft Project Reviews

We used it in my previous organization for business process optimization projects, application development projects, system integration projects, program management over a multitude of projects, and program interdependencies.

It served the purpose. It was pretty user-friendly.

I am not that close to it anymore, but I know that there were some cut and paste issues when we were trying to move one group of roles to another, and they used to muck up the interdependencies between the tiers, rows, and other things.

I have been using Microsoft Project since it was first introduced.

It was pretty good in terms of stability.

While integrating on one server, sometimes, there was a challenge. When you were leveraging the server aggregation tool, where you had everything, and you were integrating on one server to have the plans integrated for interdependencies, there was a constraint. I can't remember what it was.

A lot of Microsoft products are very Microsoft friendly, but they don't integrate well with a lot of other things. They fail in the extensibility model in the architecture design.

In terms of the number of users, we probably had about 200 or 300 people who were using Microsoft Project. In my past companies, I've had 700 people using them.

I never used the tech support for Microsoft Project.

I have used HP's PPM. There were two other tools that I have used.

It was pretty straightforward. Essentially, you should have taken classes in it and worked with it in order to understand some of the nuances of it. It can have a little bit of a learning curve.

I would advise others to look at what they have on the market because, with the advent of the cloud, so many different types of tools are coming into play that can integrate with other cost analysis platforms.

I would rate Microsoft Project an eight out of ten.

We use the solution for its Gantt diagrams and resource planning features.

The solution provides a better project view with the help of Gantt charts. As well as the resource planning features help us streamline tasks efficiently.

The solution could be easier to use. We require some assistance in case of tedious tasks.

We have been using the solution for many years.

The solution is stable. I rate its stability as an eight.

We have around ten users of the solution in our organization.

The solution's initial setup was straightforward.

Our in-house team, including engineers and system administrators, implemented the solution.

I rate the solution as a seven.

I mainly use MS Project for project planning, scheduling, and tracking.

A lot of valuable features have been added in the last three years, including scheduling automation and intelligence.

In the next release, Microsoft should include cross-project integration.

I've been using Microsoft Project for seven years.

MS Project is very stable.

This is a very scalable solution.

Microsoft's technical support is moderate.

Neutral

The setup was very straightforward and took about fifteen minutes. I'd rate the ease of setting up four out of five.

I implemented in-house.

Licensing costs vary depending on the user volume. The pricing is good, I'd rate it four out of five.

MS Project is good for anyone working on project planning and looking for a handy tool to manage everything. I'd give it a rating of eight out of ten.

I used it at another company. I'm not working for the same company at the moment. I was employed on a consultancy basis, and this product was used for IT project management.

It is a complete and all-rounded enterprise product. From a portfolio management perspective and an individual project management perspective, it is a corporate-wide project management product. It can be used for resource planning, financial planning, task planning, etc.

It is a traditional Waterfall-based solution, so it doesn't lend itself particularly well to Agile development. You can record Agile sprints within it, but it is not really an Agile-based product. It can store the basic information about budgets that an Agile set of work is looking to use, but that's about it.

I have been using it for 25 years.

Its stability, reliability, and performance are fine.

There are no problems with its scalability. 

We had about 150 users. It was being used on a daily and hourly basis. I was the program director, and all the project management teams were using it daily.

To my knowledge, I have not directly contacted them on this particular product. We had reached out to the original implementation consultants who were a Microsoft accredited organization but not for technical support. It was more for consultancy.

It was quite complicated. It needed consultants that were specialists in it to help with the implementation. Most of it was done before, but it wasn't widely used. So, we took that implementation and built on it.

In terms of maintenance, because it's a cloud-based solution, it's real-time.

It was a three-year license deal that was reconciled on a quarterly basis. It is a reasonably priced product, and I consider that we got good value for money.

I would recommend it to others, but it really depends on what they're looking to gain out of this. I would not recommend buying the portfolio management product if you do not have an established and reasonably mature portfolio management setup. If you don't have that, then you're paying for a product, but it will only get used as an individual standalone project management product, and you will not take advantage of the portfolio features. So, buying the portfolio management licenses doesn't make sense unless you've got an established or reasonably mature project office. There should be better alignment and integration with general portfolio management.

It is not a fully integrated Agile product set. It can be used to store basic information. If you've got a blend of Waterfall and Agile projects and you've got overall budgets, then you can record your Agile perspective within it, but you can't use it purely as an Agile product. For that, you'd probably use Azure DevOps or something like that.

It needs a degree of planning before it's implemented. I would recommend organizations to do that, rather than jumping in feet first.

I would rate it an eight out of 10.

We basically use the solution to get a clear sense of the project and break down everything into a schedule. If there are overlapping schedules, we plan everything out and add in all the information so the roadmap is clear. We often have different teams coming in at different times, so we need to ensure that our critical path is clear and that we are able to execute on the project from an agile perspective.

We need to be sure that we have all the backlogs and scheduling and can pull in the customer on the deliverable as necessary. We'll check with them and fine-tune everything so that we can run the sprints successfully and match them up with the project plan using Microsoft Project.

There are some valuable tools on the solution that are actually free.

The tasks are quite detailed on the solution.

You are able to easily manage other software, and, for a particular task item, you can schedule it however you like. It's quite flexible in terms of managing everything.

The solution is very complete. It makes it a great option for project managers and they can use it extensively in almost any organizational setup.

The mapping is pretty good and that's our primary requirement. Sometimes the customers and stakeholders have their own reports, but that's okay and it works for us. Most of our reporting is based on sprints and Microsoft Tool can help us map this. Most of our reporting is a combination of JIRA and Microsoft.

We can code it to JIRA and can see the total movement there as well. 

We can easily integrate it into Confluence. It's pretty seamless.

We need to know what third party solutions we want to integrate.  Microsoft by itself is a project management tool, however, if someone says they want to integrate with something else, there may be issues. Since we work on JIRA, most of the time that can satisfy our needs, as everyone has JIRA. They just update their task there and we can have full visibility.

Microsoft's solution isn't really a collaboration tool, however. If you need a collaboration tool, you can use Slack, which can be integrated with your JIRA. Any ticketing in JIRA can be integrated to Slack and you can get the messages there. 

I personally still need to compare the solution to other solutions. It would give me a better sense of if they are missing any features. Right now, without the comparison, it's hard to tell. They may need more security features, or better communication features. It's hard for me to say with my limited knowledge base.

We've probably used the solution for more than three years at this point.

The stability seems to be good. I don't recall facing issues. There aren't bugs or glitches. It's been good.

The solution is quite scalable, as far as I can see.

I've never reached out to technical support. We never reach to Microsoft support because we haven't had any problems as of yet.  Therefore, I can't speak to their level of support or responsiveness.

We also use JIRA and Confluence as part of our project management work. We usually practice agile.

The pricing is pretty reasonable. They don't seem to overcharge for their services.

We're just customers. We don't have a business relationship with the company.

I'm not sure which version of the solution we are using, or if it's the most up to date. 

We are using an on-prem desktop version. We are not using Ofiice 365. We use JIRA for project management, tasking and creating sprints. Most of the time, initially, we just create the Microsoft Project plan and then all those tasks and the PPS. We still try to deposit using Sprint. We plan it out and then run it as an agile sprint.

It's a good tool. Microsoft is quite a stable company and offers good solutions. Microsoft Project is a good solution overall. However, they can keep pushing it and offering even more features and functions in the future. It will help them stay competitive. 

I'd rate the solution nine out of ten. It's my understanding that in their roadmap they may have a plan to bring in more collaboration capabilities. If they do, it will make a great solution even better. However, they may just end up buying a project management suite and keep everything in-house under the Microsoft umbrella. It's hard to predict.

• To manage projects in the area of telecommunications and infrastructure

• The control of time and money is paramount in today's world, with this tool it is possible to assign activities, resources, periods of duration, calculation of costs, calculation of deviations, reporting, among others.

• The monitoring, control and corrective actions are possible with this tool.

• Lifting of work plans
• Assignment and effective control of the resources of the organization
• The establishment of baselines allows the project leader to take corrective actions in case of deviations.
• It ensures quality and efficiency in each activity.
• Control of project costs.

• Application of hierarchies on activities
• Reassignment of resources in case the program detects an excessive workload on a particular resource
• Comparison with the baselines
• The possibility of automating repetitive activities utilizing "Visual Basic for applications"
• Robustes in the calculation of costs
• It's easy to use.
• Combined with a project management methodology such as PMI for example, it is effective for monitoring and control.

• The productivity of resources

• The tool allows the allocation of resources to the activities, however, if I want to measure the productivity of someone in particular, it is not so simple.

I use it for project management. I use it to check the project and get some reports and KPIs from it. I am using the latest version of this solution.

It is very stable. I haven't had any kind of issues with it. It is also very scalable.

Its user experience can be improved while configuring it. Its reporting can also be better. Reporting is not very easy. Reports do not always work. I was trying to download some reports, and they didn't work. I don't know if it was related to the configuration that I was using. I didn't go too deep to check if something was missing.

I have been using this solution for more than ten years.

It has good stability.

It has good scalability. It is being used only by project managers. In terms of increasing its usage in the future, I don't have any projects going on right now, so I don't know if I will use it in the near future.

I haven't used their technical support. Its documentation and community support are very good because Microsoft has a big database.

I've always been using Microsoft solutions. I haven't tried other solutions, but I believe they are very similar. I've seen other solutions, such as Jira, being used more for agile environments.

Being a SaaS solution, it comes ready to be used. The deployment took a few minutes.

It probably was $30 per license on a monthly basis. There is no additional fee.

We didn't evaluate any other solutions.

I would recommend this solution. I would rate Microsoft Project an eight out of ten.

It's mainly for project management or portfolio projects, managing schedules and workloads, and assigning tasks.

One of the best features is that it is easy to use.

It is positioned at the more high end. Sometimes it's more complicated than we need, so we look at other solutions that might be cheaper. So, the pricing could be better.

I've been using it for around twelve months. We are using the latest version.

It is a stable solution.

It is a scalable solution.

The customer support is good. I am very satisfied. 

The initial setup is straightforward. It's just downloading the initial file version, and it can be done on the same machine. It took me half a day to deploy it. 

It can be done in-house or with the help of a third-party integrator or consultant.

I have seen ROI.

It is a subscription-based model.

It's a handy tool for budget management.

Overall, I would rate it an eight out of ten.