Microsoft Project Reviews

We use Microsoft Project for any project executions, like assigning the resource, listing out the task, and following up on the timeline. Microsoft Project is used to track the project delivery and the project management.

It would be better if the solution is integrated with other communication platforms like Microsoft Teams. Microsoft Project has a separate license from Microsoft 365 and has not collaborated with Microsoft Teams.

I have been using Microsoft Project for five to six years.

Microsoft Project is a stable solution.

Around 30 users are using the solution in our organization.

The solution’s initial setup is straightforward.

We implemented the solution through an in-house team in one month.

We have seen a return on investment with Microsoft Project because it allows us to track and execute the project successfully without much delay. Since projects are executed on time, it's always beneficial to our business.

The solution has a decent annual license subscription cost, which is not high.

I would recommend Microsoft Project to other users. As an end user, Microsoft Project provides many features like tracking the team task, checking whether the task has been completed on time or there is any delay, tracking each task, and resource allocation.

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

Our primary use case for this solution is to track our projects. The solution is deployed on cloud.

The solution has allowed us to monitor our projects in real time because it is tracked based on what has been prepared and executed.

The daily tracker is valuable because once you set it up, the dynamic teams can go and implement the project. Additionally, we can track the progress of what is being done. We can know the dates of tasks, when, and if there are deployment issues.

The product or service could be more user-friendly, and forecasting could be better. For example, a few things were added to the Microsoft Office standard software and the project online standard software. It screwed up our forecast and implementation, and we advised them to revert to the standard to fix the issue. Microsoft made some changes, and we're trying to figure out what was implemented and how to use it. We don't use the focus anymore, and we use Microsoft Project to try and drive it.

We have been using this solution for over 15 years and are currently using the most recent version.

The solution is very stable.

The solution is scalable. There are over 300 people currently using it in our organization, and we intend to increase future usage.

We have not had any contact with customer service and support.

I cannot comment on the licensing costs for this solution.

I rate this solution a seven out of ten. I advise new users of this solution to understand what their company needs. I think it's better to implement the standard software when you've understood what is required, as it is scalable and can be gradually adopted.

We actually help and assist organizations in implementing their processes, and workflows to this particular product. Suppose you want to go on the enterprise environment, then you have your own process flows, your own workflows, your own forms and configurations, your user set and your resourcing. With this solution, we can help you configure the system.

We have implemented four domains like telecom, construction, banking, insurance, health sector and pharmaceuticals. We have worked, to some extent, in each of these domains. Of course the customization, configuration and implementation varies from user to user requirements as to how they want to, and to what extent they want to do it. For example, currently I'm working for a manufacturing domain. They wanted to implement this particular thing because they want me to monitor their projects, which is running into multiple verticals within the organization and we're unable to gauge as to exactly where we are with the project status, and how we are aligned with the resourcing and the costing part.

They have their own set of workflows and processes. We help them create that within the Project Online environment, configure their process, their workflows, their information, and all the project related documentation. It's based on the SharePoint environment.  Everything that you can do within the SharePoint environment is available here as well. So content management can be configured, as per the needs and configurations and workflows.

Of course, the reporting part is a key essential for any organization. You can build your dashboards, your reports, you have a support of actual reports. You have support for PowerPoint reports, power builder. I'm not sure if you're aware of this, but all of this is supported by the environment. So you can have all the dynamic reporting and dashboards as per your requirements.

Most importantly, there are three aspects that I have seen most beneficial:

• Project tracking: This really helps the users as to where they are with each of the projects, and what are the satatus details within those projects. 

• Resource utilization: Most of the time you do not know how your resources are aligned. You cannot take up projects because you do not know whether this set of resources are available to you within that particular time frame. If you have all your resources within the enterprise environment, just one click and you are able to see that this resource is available during a specific time. So, I can pick up this project and assign this resource.

• Cost: Most of the time, we're unable to note exactly how much cost has gone into the project, because some of the numbers go into the documents that we put in, but the real numbers are really not captured all the time. Here, you will be able to capture your manpower cost, your material costs, your travel costs, and any other costs that's associated with your project and see that as direct impact on your project progress. Half of the time you might have a certain budget for it, but because of mismanagement within the project, the increase of scope and other such reasons, you end up spending more than what the budget really was approved for you. You are able to capture and see: financial status, usual status and project status.

So far I haven't faced any issues with scalability because everything that we have wanted to achieve, we've been able to. It is a scalable product. I've worked in multiple domains, and each domain has its own set of requirements.

We have close to like 5,000 all users. That was a really huge implementation, and we had to get into a firm deployment and that went on to like 14 servers also, because there were so many services and so many other things that you needed to put in place, and of course give it to high availability and high performance also.

Usually we have this onsite and offshore supports in place. At the onset we prefer an onsite support because that's more like filling in the knowledge gaps that the users will face, because they do not know the environment, they do not know the working of that environment. Then with the stability as the time moves, like a month or two months down the line, we turn it into an onsite offshore support with reduction of resources. That's totally based on your other kind of user base you have. Like for example, currently I am catering to a user base of approximately 1,000 up people and we are doing an onsite offshore support. A few people are placed on site to help the user immediately take care of their concerns, and some people are working at the offshore to take care of whatever comes into the hill test environment and then manage that. This depends on the organization's requirements, but you have both the models available. The response has been really wonderful.

It's a straightforward deployment. If you're going into a Project Online, you don't have to do any setup. It's just the basic configuration, which I will be connecting to your active directory to pick up your resources, and I will be configuring the environment for role security permission and stuff. Then of course, the custom information like your verticals, your divisions and stuff that you want to align your projects with. So the configuration is very easy. Of course, only if you want to bring your own workflows and customization into the environment. That's the development rule, but even those development periods are not very long. Like four months, five months is max that we get into. After that, just mostly support and enhancement.

There has been a lot of improvement in terms of the return on investment for ordinary resources, as well as the costing. We were able to see that the same project which they completed earlier in six months, now they could timeline and complete within like three and a half months time, or four months time with the better utilization of resources. Along with that, they were able to have their projections also in place, that pipeline also in place. Like you don't just have the projects in here, you also have the concept of proposals in here. So automatically, you know that these products are in the pipeline in form of proposals, and they will be executed within the timeline. 

The standard diversion of Project Online or Microsoft Project, is that it automatically has so many built in features that you really do not need to invest much in terms of trying to configure it to suit your requirements. It has all the standard practices, built in practices, all the pin book concepts already aligned within the product.

There are some serious competitors in this sector. For instance, there is Clarity from CA, Planview and  HP PPM. These are some of the other competitors that you have on the market. I think the Microsoft products are very user friendly, the ease-of-use is an asset.

The only drawbacks are the customization. Generally what happens is everybody wants it to be an automation tool, and this is not the use case for this solution. It is a platform for project management. You don't want an automation to be in place.  The system does not do it automatically because you as a project manager are expected to see that the input received, the status received from your team members is correct and accurate. Then that information is available for the rest of the team. You don't want that to be automated. So when the user comes back from this kind of mindset that everything should get automated, then no. I will not suggest that because this is management, this is project management.

This is not an automation tool, although to a very large extent, a lot of things can be automated to workflows in other ways. If that is your requirement, might as well go and build a custom tool yourself if that's what you're looking for. Then even that won't help you because project management is so related to so many other things that you'll not be able to encompass that all within the environment. You won't be able to think of that. I have been working with Microsoft for 18 years now. Obviously, their experience and understanding of project management would any day be more than any other solution.

We use Microsoft Project for its timeline and task management capabilities. The primary advantage is the easy application of tasks in sequence, confirming dependencies, and establishing relationships between tasks. It simplifies handling conditions, significant dates, and dependencies between various tasks.

The tool's most valuable feature is scheduling. 

Microsoft Project's reporting is very complex and not user-friendly. 

I have been working with the product for ten years. 

I rate the tool's stability a nine out of ten. 

The tool's deployment is very straightforward. 

I rate Microsoft Project's pricing a five out of ten. 

I rate the solution a nine out of ten. 

The primary use case of this solution is to help plan the work and implementation plans for our projects.

I find all the features of the solution valuable.

The solution is currently a bit slow and can be faster.

I have been using the solution for one year.

The solution is stable.

The solution is scalable.

Before switching to this solution I used online tools to help with our project implementations and monitoring tasks.

I believe the licensing for the solution is based on an annual fee.

I give the solution an eight out of ten.

We have over ten people in our IT project department that currently use this solution.

I recommend the solution to everyone.

It is easy to define timelines with Microsoft Project. You can get a clear picture of the model, you want to create.  You can create inside an agile or waterfall model. Microsoft Project is easy to delegate tasks to different members where you want to put the task and who you want to work on it so that you have a clear path.

Right now you can create a timeline with the major up tasks, but there's no real way to mark it. When you are planning, you usually have resources on board for a single task.  Microsoft Project has no way to mark it because it is based more on agile methodology. Many times you want to take it by the resource count and that is where it becomes tricky. 

 I would like to see an entire baseline, like in JIRA. It is like project planning in JIRA, but there's a whole story building that you can do. Microsoft Project needs to incorporate some points of story-building and epic building, which are currently missing. 

I have been working with Microsoft Project for the past month.

Microsoft Project is a stable solution.

There is no problem with Microsoft Project's scalability.

I do not use Microsoft technical support because our company has its own technical support team.

I only use a login feature for Microsoft Project. 

I would rate Microsoft Project an eight and a half out of ten.

We primarily use the solution to enter our status and our time. For each task that we're doing, we have to enter a monthly status. It's for project management.

Overall, the solution has been so much better than the previous project management tool we had been using.

It's very easy to select the projects. It's so easy to save the project, task, and hours that I want. You don't have to think about it. 

The user interface is so clean. The previous EPM product was so hard to understand in terms of the user interface.

Once we commit our status, changing it is hard. Sometimes, I may make a mistake about a holiday or something. I may not remember that there was a particular day that was a holiday and I may enter time on that day as if I worked. Sometimes I want to fix it. It would be ideal if the holidays were pre-installed so that we wouldn't make that mistake, that would be ideal. It should allow us to set it so that we cant enter time on holidays. 

I have only explored maybe 5% of Microsoft Project as we're only using it to log things. I haven't seen a lack of features.

I've been using the solution for about one year at this point.

I haven't had any issues with stability. There aren't bugs or glitches, at least, none that I have witnessed. It doesn't crash or freeze. Overall, it's quite good.

Every employee has to use this solution, and we are a sizable organization. Likely, we have thousands of users on this product.

The solution is on the cloud, and therefore it can scale so well. We have our own internal cloud, and Microsoft has a cloud as well. If a company wants to expand it, it should be able to do so with relative ease.

I can't speak to the quality of Microsoft's technical support. I've never contacted them, so I can't say how knowledgeable or responsive they are. We have our own internal support. We are a very big organization, so we have an internal support team that assists us if we need help. They may reach out to Microsoft directly, however, I have no knowledge of their interactions.

We did previously use a different project management solution. I've only seen the user interface. It's my understanding that it is called EPM, or something to that effect. I like Microsoft's solution much more. It's a better product.

I only use the solution. I did not have to set it up. I can't speak to how easy or difficult it is to do this as I am just an end-user in the company.

I'm an end-user and customer. My organization is a large company and we're a big customer of Microsoft.

I don't know which version of the solution I'm currently using.

My life has improved so much with Microsoft Project. It works extraordinarily well.

Overall, I would rate it at a nine out of ten.

The primary use case of the solution is for in-house IT projects such as network projects, and system projects.

The most valuable feature of Microsoft Project is planning.

The licensing cost for Microsoft Project is expensive and has room for improvement.

The initial setup is complex and has room for improvement.

I have been using the solution for several years.

The solution is stable.

The solution is scalable.

The initial setup of Microsoft Project is complex.

The deployment took one day.

The implementation was completed in-house.

The license for Microsoft Project is a one-time payment but it is expensive.

I give the solution a six out of ten.

We have 20 people using the solution in our organization.

Two people are required for the maintenance of the solution including one manager and one engineer.

I recommend the solution to other users.