Whenever we have a client with a complicated situation, we create a project plan. And we use Microsoft Project (MS Project) for administrating, monitoring, and tracking the project. For most small projects, MS Project is satisfactory.
We can input information and then share it with the project team and stakeholders. That helps a little, but if somebody changes their mind, it could change how we manage the project. There are some new features in MS Project 2021. However, more features aren't necessarily useful because now you must train people to use them. They may say, "Why do I need this new feature?" Newer versions of MS Project display a warning when a task runs behind schedule. However, it is necessary to input a date change for that warning manually, and administrative action takes precious time.
It's possible to get input from other programs, such as Outlook, but we don't use Outlook for anything other than email, even though it could do other things. Time is a critical resource. We don't have time to learn about these features and use them productively, so they are of no value to us.
MS Project's resource leveling capability is beneficial. We like this feature. We want to be able to expand tasks and look at different resources and task usage. It is good at assigning tasks to teams.
It's generally compliant with the Project Management Institute approach to project management, which means MS Project helps us be more uniform and consistent in conducting each project.
MS Project can insert objects, like a drawing or an Excel worksheet, but cannot handle business rules. Also, I would like to see better integration with graphics applications such as MS Visio. The graphics are primitive and need some major work. I would like to have the ability to insert some small macros within the project for Monte Carlo risk analysis. For example, if you're unsure how much time a task may require, you can generate a reasonable guess.
MS Project is very time and labor-intensive to keep current. You need to update it continually. You may find that you are spending more time maintaining the MS Project file than working on your project. I don't want to devote a person to do that.
MS Project should have the capability to link it to other applications to make the program dynamic when a real-time resource or schedule changes, but it is not dynamic. It would be helpful to insert real-time input data for each project, subproject, or task. If something is going on, I want to see the impact in real-time, if possible.
I want to be able to specify globally what weekend we want or what we want to call a weekend. Also, we might have a project underway seven days a week.
External data sources, like third-party manufacturing processes, impact some tasks. Embedding external processes within MS Project is almost impossible because we don't have programming resources here in a practical sense. Also, the interface of Microsoft Project is proprietary. We want to link different tasks to external sources of inputs and outputs and integrate them automatically with our master project plan, e.g., specific third-party CNC machine data. The supplier's system does not interface with ours'. We have to get the outputs from their system serially and manually update the MS Project file to determine the schedule impact. That takes time. There is a risk of data entry errors at both ends. On tight projects, every minute counts.
I would like to see a control system interface with Microsoft Project. Real-time system data helps predict cost and schedule variances. For example, if you had to finish a day ahead of schedule, you could "talk" to the systems' software and determine if a given machine works for another four hours, then you could meet the accelerated schedule. MS Project requires manual data entry with a risk of mistakes. Presently, there is no automated data entry capability in MS Project. It just doesn't exist. That's why I say it is only suitable for small-sized to medium-sized companies and small projects. Most companies don't have the same problems we have with MS Project.
When you're working on a project that has to get done, you will spend most of the time wrestling with Microsoft Project, whereas you should be using these hours to manage the project.
Thinking on a slightly bigger scale, I would like better integration with Office, Visio, and Access. If you make a change in one application, it should cascade to others and vice versa. It doesn't do that, at least not easily. It is not a dynamic program. I would like to see an active program or at least the capability to be dynamic, even if it is close to real-time where it outputs to a module, and the module then talks to real-time systems. The real-time data goes back into the module, and the module updates the project plan. Such dynamic capability would be superior to what exists now. It may not be genuinely real-time, but it is at least closer to it.
I want to link directly to the data in an Excel spreadsheet so that I don't have to keep going back and forth updating it. I don't want to have to create a dynamic link library or write a macro. Whenever I change the data in an Excel file for a given project or task, it should update the corresponding Visio or PowerPoint file. If I'm doing a pie chart or any graphic, I don't want to manually update my graphics. I want to link them together, and I want them updated automatically. I know it is a wishful thing. Microsoft doesn't make significant changes every time they come out with a new version. However, they don't appear to fix the issue. Instead, they add a few features.
I have been using Microsoft Project since it was released in the mid-1980s. Although MS Project can be helpful, it does not teach project management.
It's relatively stable. I've never had a crash. I can't remember it ever crashing. If I entered some information that it can't resolve, it usually comes up with an error message.
I think it is limited to around 400,000 tasks. I am not sure. I never had to go that far. We have five consultants who are remote users.
I've never really needed any support. When Microsoft has a seminar or a meeting locally, I might go to it and give my feedback.
Installation is automatic and simple, we had no issues.
The implementation was done in-house.
MS Project pays for itself by helping me keep my thinking straight. The purchase price of the application is insignificant when compared with the time involved in trying to do project management manually on paper attached to large poster boards. We did it that way before the advent of PCs. There is some benefit to seeing an entire project plan on paper to provide a visual idea of project scope and progress, but intelligent use of MS Project can generate the same information. It takes a lot of time to become so proficient with MS Project that these key bits of information are generated automatically through accurate and complete task definitions, WBS, and project schedule updates.
Make sure you have a good business reason for purchasing MS Project. It isn't cheap and there are free alternatives, with simple capabilities, available.
MS Project was sufficient for our requirements, so we did not evaluate any other options.
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 are minimal capabilities to help you write routines. So, you have to change dates and task names. If you don't understand project management concepts well, 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've made comments about it at some seminars hosted by Microsoft. We've 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's 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.