Prioritizing the Project Portfolio
There seems to be no end to the grinding and mashing of teeth when it comes to prioritizing projects into and within the IT project portfolio of an organization. Typically the pain found in many prioritization efforts is due to the lack of a consistent, objective and measurable method--thus leaving only persuasion and politics to guide the effort.
This is not to say there are not a host of issues and challenges related to the prioritization process, some of which that seem to defy objective quantification. Issues related to:
- Risk of Failure
- Windows of Opportunity
- Regulatory Uncertainty
- Regulatory Urgency
- Resource Scarcity
- Risk to Capital
- Economic Uncertainty
- Competitive Positioning
…and more can make the effort to achieve clear and concise prioritization criteria seem daunting (if not impossible) to achieve.
If only it were as simple as prioritizing projects based on the best return on investment. But even ROI can get muddy due to faulty estimates and over-exuberant value propositions. And what about changing the priority of projects once they have been started? How do you quantify disruptions to progress, impact on morale and
Please log in or sign up below to read the rest of the article.
|
"It is best to keep your mouth shut and be presumed ignorant than to open it and remove all doubt." - Mark Twain |




