What advice do you have for others considering Microsoft Project?

I rate Microsoft Project a seven out of ten.

I'm not using it directly, but I work in Cognizant, and some of my clients use it. We are doing some work on observability, and I was comparing the tools. I can't provide feedback because I haven't used it and haven't got some in-depth knowledge of it. I am not aware of MuleSoft Composer. We haven't used MuleSoft RPA. That was mostly in the past when I worked as a product developer. I am just an end user for Microsoft Project, but our company is definitely a partner with Microsoft. I would rate my overall experience with Microsoft Project as nine. I would prefer to remain anonymous, so I won't share much because I'm not sure whether my organization allows me to share such feedback.

Previously, during my service as part of portfolio management, I heavily used all the Microsoft tools. I used quite a variety of tools, but not now. I'm transitioning the portfolio and the company to Google and other alternatives. If Microsoft can reduce its prices, it would be greatly appreciated. The free version is also limited. I would rate the product eight out of ten.

For complex projects, I recommend using Microsoft Project due to its superior scheduling and dependency mapping capabilities. For simpler projects, consider other options.

I'd rate the solution nine out of ten.

I rate the overall product a seven out of ten.

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.

Microsoft Project is deployed on the cloud in our organization. I would recommend Microsoft Project to other users. Overall, I rate Microsoft Project a nine out of ten.

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.

I recommend this solution to those planning to use it. Microsoft Project's potential users should plan their projects well enough before planning to use it. In general, Microsoft Project is one of the best tools available in the market. I rate the overall solution somewhere between eight and nine out of ten.

The solution is easy to use but needs to be more comprehensive. I rate it as a seven.

I would recommend those planning to use the solution to learn to use it from somewhere since, for beginners, it may seem like a complicated solution to use. I would absolutely recommend Microsoft Project to those planning to use it. Though the solution serves my purpose, it is a bit costly. So, I rate the overall solution a nine out of ten.

I am not sure if we are using the latest version of the solution. I'd recommend the solution to others. I would rate it eight out of ten.

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.

I highly recommend the solution due to its ability to enhance organization and improve task management within projects. It is possible to stay informed and up-to-date with any delays or discrepancies in the work being done. The solution is immensely valuable. I wholeheartedly endorse this process. I rate Microsoft Project a seven out of ten.

I would tell potential users that Microsoft Project is acceptable if they run a Waterfall project. If they are trying to do something more Agile, they will probably want some other capabilities that the other tools provide, like Kanban tools. It does what it does, but when you compare it to the tools with Agile capability, they work based on tasks and resource availability. They usually have backlogs of different activities, and the team will decide which ones they want to work on next. Every two weeks, they have a periodic cycle, and they look at the backlog list and pick from there which ones they want to build next. This may not be how they were first defined in a typical Microsoft Project Gantt chart. On a scale from one to ten, I would give Microsoft Project an eight.

Microsoft Project is a good tool. It is very easy to integrate and set up.

I haven't used it extensively. If I had used it in the environment where I was working, and I was responsible for the task I was doing, I would've experimented more on it and figured out something. However, that's not the case. We are aware of how to install certain processes exactly and how to use those processes in Microsoft Project. However, you'll have to spend at least a week or two days at minimum to see how everything works and what kind of allocation works best. There are a few things that you need to be specific about. With Microsoft Project, it becomes easy to use when you know what you're doing. Using the product will not be a big challenge if you are comfortable with project management. I'd rate the solution nine out of ten as it was easy to learn and a very useful tool in general.

I recommend the solution and rate it a ten out of ten.

I was an end-user of the product. Overall, I would recommend the solution to others to use. I'd rate the solution eight out of ten.

It is pretty straightforward. There isn't anything heavy about it. I would rate it an eight out of ten.

We are customers and end-users. I'd rate the solution seven out of ten. I would recommend it for companies that have a large number of projects and diversified teams. When I say diversified teams, I mean geographically spread and working on multiple projects. Those are the kind of people who could make use of Microsoft Project very well.

I rate Microsoft Project seven out of 10.

I recommend using this solution if you working on a complex project or complex system.

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

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.

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.

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

I would advise others to concentrate on the culture and skillset of their team before implementing a project management tool. I would recommend this solution to others. I would rate Microsoft Project an eight out of 10.

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.

You have to find the right tool that helps make it easy and streamlined for you to manage. You just need to find the right platform. I would advise others to get out there and play with all of them and then find the right one. Do tests with them, and then figure it out. That works best. I would rate Microsoft Project an eight out of 10.

I would advise others to learn about project planning. There is good enough information available online on Microsoft's website. I would rate Microsoft Project an eight out of ten. It is good at doing what it is supposed to do.

We are customers and end-users. I'm not sure which version of the solution I use. I don't use any advanced features. I basically put in tasks and assign resources, and assign predecessors, and successors. That's about the level I use it at. I don't do tons of work resource balancing, or Gantt charts out of it or anything like that. I would rate the solution at an eight out of ten. It more than meets my needs for what I'm using it for. What a real project manager may rate it might be different.

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're working with the solution's latest version. However, I'm unsure of which version number we're using. I'm not sure of the deployment model. It's more of an application than anything cloud-based. Overall, I would rate the solution at a six out of ten overall. It's a cool type of tool, however, there are some improvements that can be made to make it better. It could be simplified. The best thing before asking these questions is to go through the UI. It helps you to have a picture of what the tool does.

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.

When choosing this solution understand that is it best for those who want to stay with the Waterfall framework. First-time businesses in some industries such as construction, Waterfall is a better choice. It depends on the industry, but the majority of industries and companies are moving to Agile methodology. I rate Microsoft Project a six out of ten.

Microsoft Project is the best. I would recommend this solution to others who are interested in implementing it. It's important to get the appropriate training. I would rate it a ten out of ten.

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

I would suggest using an expert. Get an implementation vendor to set it up for you. This solution probably does everything that I need it to do, but I just don't know how to do it yet. I like Microsoft Project and it does everything that I need it to do, but it doesn't do everything. That's Microsoft; they always get you to about 80% there, and then you need some type of plugin or API. It never quite does everything. I would rate Microsoft Project an eight out of ten.

It is a mainstay product. A lot of people use that as their first introduction and it's not meant to be a project management ERP solution, like Life Clarity or the others but it is a capable product that establishes a framework and a basis that can be used across the industry. I would rate Microsoft Project a seven out of ten because you'd have to have in-depth knowledge of the tool for it to really be beneficial to you. It also allows the new developers and new project managers to come in and be proficient and be able to develop schedules fairly readily. From that standpoint, it's fairly strong. From the overall usability of the product, it can be cumbersome.

Make sure you understand what MS Project can do and what it cannot do. It cannot read your mind. Just like any other program, it only does what you tell it to do. If you give it the wrong information, it will provide you with incorrect output. It is very labor-intensive. There is minimal capability to help you write routines. So, you have to change dates and task names. If you don't understand project management, you're just going to delude yourself into thinking MS Project helps you. You have to understand the process of project management to use the application effectively. Otherwise, you are wasting your time. It will not teach you how to do project management. I would rate MS Project a five out of ten because it hasn't evolved that much. Microsoft added lots of bells and whistles, but they don't add much new value. They don't save me much time. I want MS Project to be a dynamic program, but it remains a passive program after more than 30 years. I have made comments about it at some seminars hosted by Microsoft. We have told them to make it a dynamic program or at least have an option to make it active. We would be willing to pay more for this capability. It is worth it, but they don't do it. I guess they don't see enough business potential in doing it that way, and I don't have the resources to create an internal application to make it that way. I am not in that business.

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.

I would recommend the solution to other companies. It's worked fairly well for us overall and we've been satisfied with the experience we've had using it. I'd rate the solution eight out of ten. There are still some items that could be better. It's not a perfect solution, although it's pretty good.

This is a good product and I can recommend it to others. I would rate this solution an eight out ten.

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.

My suggestion is to do homework and compare what other products are out there and how well they will fit with your organisation. This one's okay. I've personally used a range of different products, all potentially good choices, it just depends on the operating context and culture of the organization whether it's going to fit, or not.