Which PPM Functions Really Create Value?
From the Project Management 2.0 Blog
by Dave Garrett
New technologies, concepts, and Web 2.0 tools are popping up everywhere. How can you use them to help your project team collaborate, communicate - or just give your project an extra boost? [Contact Dave]
Recent Posts
Are You Prepping For The PMP 24/7?
Are You Just Too Darn Busy?
Eliciting Requirements... Creatively!
What To Expect When Your Stakeholders Are Expecting
8 More Templates to Save You Time
Categories
Advice,
Certification,
Collaboration Tools,
Decision Making,
Estimating,
Interviews,
Learning,
Management Approaches,
New Templates,
Personal Productivity,
PM Software,
PPM Software,
Presentation Tools,
Reporting Tools,
Requirements Management,
Research,
Risk Management,
Scheduling Software,
Security,
shameless self promotion,
Techie Tools,
Time Killers,
Time Tracking Software,
Training,
Virtual Team Tools,
Web-based Tools,
workshops
Date
Situation: You are asking yourself, "What do I really need from PPM software?"
I've been asked this question a lot lately. So I thought it deserved to be addressed here, in a way that hopefully the asker can relate to. The answer of course, is "it depends". It depends almost entirely on the maturity of your organization.
Even for something as important as "doing the right things" (PPM), most of us feel like we really only need a few key functions. With this in mind, software vendors have spent the last few years creating simple SaaS applications to serve our needs - each of them focusing on limited views of the portfolio that should be just enough to facilitate decision-making to accomplish mostly near to medium-term goals. Despite most of us having some similar basic needs, we still customize whatever we end up implementing. Since a lot of that customization ends up happening (i.e. - is funded) when the software is first bought, we end up optimizing the software for the needs we have NOW, versus longer term considerations. Then we consider the PPM Project done. Later, when PPM is less of a hot button at your organization, it becomes harder to have the system evolve as the company matures.
So let's talk about the things companies generally want. I'll begin with a list of PPM functions from MS Project Server 2010. It a set of information management areas which are fairly comprehensive, yet their value probably varies a lot based on what your immediate needs are:
How much do these matter to you? If you are really having a problem "doing the right things", the prioritization might look like this:
-
Portfolio Selection and Analytics
-
Business Intelligence and Reporting
-
Demand Management
-
Financial Management
-
Resource Management
-
Schedule Management
-
Time and Task Management
-
Team Collaboration
-
Administration, Scalability and Extensibility
However, if your real problem is just not having enough people to get everything done (the situation most PMOs find themselves in), you might have a view that looks like this:
1. Resource Management
2. Schedule Management
3. Time and Task Management
4. Team Collaboration
5. Portfolio Selection and Analytics
6. Business Intelligence and Reporting
7. Financial Management
8. Demand Management
9. Administration, Scalability and Extensibility
I often hear from organizations where project management itself is not part of the corporate culture, then time and task management are at the top of the list. Almost universally, senior management would like everything fixed immediately by the new system - so most people are just trying to implement all of these functions. Unfortunately, the functions are just the means of getting there. Implementing functions individually doesnt really help. It's how they comes together to form a complete system that creates the value you are looking for.
So you might be thinking, "it depends", isn't very helpful. The key to getting the most value out of your PPM solution is understanding the PPM maturity of your organization and using that as a guide to rolling out new technology and processes. It's more about looking at where your company is and what you can accomplish when, changing the focus of your efforts as the organization matures.
Gartner, some time ago, laid out a roadmap for doing just that. It is available here on gantthead for your reading pleasure. You'll find that the maturity levels are not a direct match with the function, but rather imply that you focus your efforts in certain areas at different points in time. There are dozens of other resources here on gantthead, a few of which I've listed below. Hopefully these will help guide you ithrough your PPM journey.
Also See:
Posted on: June 08, 2011 07:09 PM |
Permalink
Comments (9)
Please login or join to subscribe to this item
Andy Jordan
President| Roffensian Consulting S.A.
Cherry Grove, AB, Canada
Too often companies are looking for that 'silver bullet' solution because they need help improving the quality / consistency / effectiveness (all of the above) of initiatives that are currently struggling. Like any other aspect of evolving maturity there needs to be careful consideration of not just what a tool can do, but also how ready the organization is to use the tool. This is a great post that shuld be mandatory reading for anyone with a line in their budget for a PPM tool!
Josh Nankivel
Engineering Project Manager| Apple
Sioux Falls, Sd, United States
I think change management is something that doesn't get enough attention, in PPM solutions or elsewhere.
First, understand that change management is different than configuration management. The two get confused far too often, and in general they both get buried under "Integration Management" and simply don't get the attention they deserve. They also happen at various levels; at least one level for individual projects and another level for the project organizational processes themselves. Many organizations do a poor job at the project level and a hideous job at the organization level.
Much of the reason why organizations struggle with projects, especially through growth and changes in maturity, is that the functions of change management and configuration management are buried and forgotten, and left for people to shoot from the hip.
Josh Nankivel,
pmStudent.com
Brad Egeland
Business Solution Designer| Bradegeland.com
Las Vegas, Nv, United States
I agree with Josh. Change management seems to be this grey area functionality that is either often not addressed or left entirely up to the project manager who also has a thousand other tasks to do while meeting every daily challenge thrown his way.
--------
Brad Egeland
http://www.bradegeland.com
Ooh, I wanted to be the first one to mention change management! This is an area where software can really help. In one of my old jobs we had a workflow tool that stepped you through the change, ensuring the right people approved it and that everyone understood the impact of the change. Now, all of that is done on a paper form, or not at all. Ensuring that stakeholders really understand what they are signing up for when they say ''Can we just do this?'' would be a big step forward.
--
Elizabeth Harrin,
A Girl''s Guide to PM
I agree with the posters around the change mgt idea. When approaching a PPM solution there is certain functionality that I consider to be 'standard' and 'out-of-the-box' whether packaged or SaaS. What I struggle with of late is how to address:
Demand Mgt - and keeping the list of screened, qualified projects available as the next best ones to start
PgM Scheduling - It's great to get an individual project schedule out of a PPM tool, but what I really need is one that looks for dependencies (and does a better job of managing them) between projects (e.g. if Proj A is late how many other are impacted)
Resource Scheduling - Needs to be integrated with the master resource plan for the entire IT shop becuase every resource is (usually) matrixed between projects and support. To look only at projects gives you a one-sided view.
I really like the framework and Dave's points are right on regarding where an org is on the PPM maturity scale really drives your other priorities. Great post!
Wai Mun Koo
PMO Director| Intergraph PP&M
Singapore, Singapore
I agree with Tom on the Demand Mgt with a point to add.
Demand Mgt - We need to have a mechanism to determine what constitute a project. Sometimes, the demand may be something really small and could be easily handled by a single resource within a week vs. a project that needs 30+ resources over a year. We need a sizing mechanism here.
Also, when a project is completed, it shouldn't just end here. Sometimes, we need to monitor this project, especially from a benefits and ROI point of view, for a certain period (say 12-24 months) to justify its value to the stakeholders and sponsors. Would be good to have a function for the project manager to monitor and track the project after its closure.
Agree with all of the above :)
All those functions succeed or fail by the use of the system. So I hope to see a lot of intuitive design and other ways to make the functions accessible to everyone.
Mike Donoghue
Technical Communication, Marketing, and Training Initiatives| New! Improved! Communications
West Hartford, Ct, United States
A great list -
As Dave states that "it depends" when it comes to those PPM functions that create value, it also applies to two types of projects:
* Big "P" projects (those for the benefit of the organization as a whole); and
* Small "p" projects (those for the benefit of the project and solutions they provide).
Joe Wynne
Retired from Banking
Charlotte, NC Area, United States
My experience leads me to prefer Dave's second list with the top two items being Resource Mgmt and Schedule Mgmt - but not necessarily because of constrained resources. Like Elizabeth above, managing the changes in resource availability and required tasks over time drives that preference. My projects have tended to be parts of larger organizational initiatives where the multiple projects start at basically the same time, but probably should not be, so adjustments have to be made on the fly.
Please Login/Register to leave a comment.
|
If you haven't got anything nice to say about anybody, come sit next to me.
- Alice Roosevelt Longworth
|