Have we clearly defined and communicated the portfolio priorities?
Clearly defined and communicated priorities enable program and resource managers to make decisions regarding the appropriate allocation of resources in the event of a conflict or schedule slip. Getting “I want is all” executives to define priorities is often a challenge, but being clear about priorities ensures that the most important work gets done.
Priorities are not about what to do first or what to kill. In portfolio management, priority has a specific definition. The definition is: If the timeline or scope of a high priority project is in jeopardy, and if the problem can be solved by temporarily taking resources from a different, low priority project, then those resources should be temporarily re-tasked to the high priority project to keep it on track.
Rather than force ranking all of the projects in the portfolio, I suggest forcing a distribution of projects into quartiles or quintiles. The lowest classification of projects in either scenario are still important. If they are not, then they shouldn’t be in the pipeline in the first place. By forcing a distribution, you ensure that all stakeholders are clear on the priorities and can act accordingly without intervention.