Our last article discussed the 4 main classifications of tools, as we see them, for teams that believe they have outgrown the applications current supporting their projects or portfolio.
In this article, we’ll actually discuss what teams might need to consider in order to come to a conclusion about which tools suit their requirements.
Caveat: Agile is not considered here. If your organization is investigating a move to an Agile development methodology I would urge you to read articles written by people who have real experience with Agile (and the battle scars to prove it), like this one.
Typical considerations for inclusion into the requirements of a Project and Portfolio Management System (not all inclusive):
- What data are the project managers and schedulers responsible for estimating and managing?
- Activities and Milestones – generally a given
- Progress – where are we?
- Baselines – how are we doing against our estimates and what has happened since our last update?
- Resources – Who is doing what? Do we have what we need?
- Cost – What will this cost us? How are we tracking to the estimate?
- Other attributes? – There are probably an unlimited amount of things that you could think to track on a project. What do you need to keep tabs on?
- What level of detail and accuracy is required?
- Are you creating and managing high-level plans or are you producing and tracking very detailed plans that are updated several times daily?
- What is the impact if the plan isn’t exact?
- What are the communication/reporting needs?
- Will data from multiple plans need to be collected/integrated into one place?
- Will reports need to be produced using all data within the system?
- Who are the audiences that will need to review the data and what do they require?
- Will actuals for resources and cost need to be collected and reported?
- Does the organization need any level of standardization?
- Does the organization have the ability to hire an administrator?
- Many of the PPM tools must be “built” or configured (to a certain extent), beyond their out of the box capabilities. Who will do that?
- As the platform stabilizes this workload will go down, but the initial lift will be significant and must be accounted for.
- What will the new applications require in terms of training?
- What is the capacity of the organization to learn new applications?
- Do the new application vendors offer training and at what cost?
- What are the technical requirements?
- What is the mechanism for download and installation?
- Are there different versions of the application (desktop vs. server)?
- How often are upgrades introduced and how will they applied?
- Will upgrades cost anything?
- How is the application licensed?
- How much of this application will our organization actually use (try and achieve a percentage)?
That last question is critical in that many organizations often end up with a tool that is much more than they will ever need or use. The crux is estimating and tracking resources and cost. If your company MUST have this, then you need a project or portfolio-level application, because your needs fit what those tools were made for.
If your organization is a bit loose on resources and cost as it relates to projects, then you can get away with a pure project management-level application, since you’ll be focused on scheduling and reporting.
We’d be happy to jump on the phone and help you figure out what might be best for you, and would also love to hear about any of your past experiences on this topic! Please post a comment or feel free to email us anytime at email@example.com. Good luck!