Microsoft Project Reviews

They have moved from a paper to a project management tool. That's the big change. Earlier, they were using papers and then they started using Project Professional to run their project server, it's a huge change and a huge transition.

I think they've begun to improve with the new cloud integration. Previously, this was an issue. Now, I don't think there are any further changes that need to be done for the cloud issue.

There needs to be better integration between SharePoint and other Microsoft platforms and this solution. Furthermore, there should be a better integration with the use of the cloud and mobile devices.

For individual users, I don't think there is a stability issue. I've not really seen any performance issue with that.

The tech support needs improvement.

The setup was straightforward. It took us about three hours to do so. 

I do not have personal experience with pricing or licensing of this product.

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 am a utilities consultant, and I use it within the utility industry for managing different types of projects, such as for implementing a new system or new processes.

I don't know how it directly benefits our business per se because it helps our clients.

It is easy to use and pretty intuitive. User interfaces have stayed the same for the most part for the last 20 years. So, there is a familiarity.

Its reporting and its integration with some of the other related systems should be improved. It is not very easy to integrate.

Its scalability is not so good for the most part.

I have been using this solution for altogether 20 years.

It is pretty reliable. I can't recall any issues.

It is not so good for the most part. It is good for what we needed it for. Occasionally, we needed to be able to scale it up, but it is not as effective as some of the other systems.

We have around 30 project managers who are using it. We're all dispersed across the US, and it is being used extensively.

We have no experience with them.

I've used other project management solutions. Its simplicity and ease of use are the primary drivers.

The initial setup was straightforward. I didn't do it. Our IT guys did it, but once they got the process done, it took less than an hour.

We just did it ourselves. For its maintenance, we require probably a fourth of a person. 

As with anything, there is training, and there are standards. Make sure you have enough training and make sure you've established enterprise standards.

It is reliable, and a lot of people know it. I would give it a seven out of 10.

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.

I use Microsoft Project to manage project timelines.

Microsoft Project should provide better documentation regarding the usage of the solution.

I have been using Microsoft Project for the past five years.

Microsoft Project is a pretty stable solution.

I rate Microsoft Project an eight out of ten for stability.

It depends on your system's RAM, but Microsoft Project is scalable. Three users use the solution in our organization.

I rate Microsoft Project an eight out of ten for scalability.

I previously used the solution called Trello.

Microsoft Project's initial setup is straightforward.

Microsoft Project was deployed by the IT team and my office administrator within thirty minutes. You can just install the solution and start using it.

The ROI with Microsoft Project is good as there's a real need for the solution.

We have to pay for a yearly license for Microsoft Project.

I would recommend Microsoft Project to other users and ask them to get trained to use the solution.

Overall, I rate Microsoft Project an eight out of ten.

I was using this solution for project planning and status reports for a work project I was involved in.

Microsoft Project is user-friendly and easy to use to do very complex project plans.

The dashboard could be improved.

I have been using this solution for six months.

The solution is stable.

I have found the solution to be very scalable. 

We had evaluated other solutions before we chose Microsoft Project, such as Clarizen. Based on our discussion with the client, we decided to go with this solution.

I rate Microsoft Project an eight out of ten.

We use this solution with CA Clarity PPM.

With well-constructed templates that include milestones that allow upper management to effectively measure progress, the dependencies between project and external activities that often diminish project success can be mitigated.

Dependencies (not typically effectively used in "Agile" techniques) allow understanding of actual project status and challenges.

This solution needs more templates focused on types of projects to ease setup.

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.