Project Rankings - TechRepublic
General discussion
November 9, 2005 at 09:48 AM
larryjg

Project Rankings

by larryjg . Updated 20 years, 7 months ago

I have worked with several clients (IT Managers, CIOs) that have maintained a list of their top projects in order to provide direction to their organizations and to report up to their senior management. I have repeatedly seen these managers use duplicate values when ranking their projects i.e. Project A=1, Project B=2, Project C=2, Project D=3, etc. My perspective is that if the intent is to truly provide direction and to validate to upper management the appropriate alignment of effort to strategic objectives, then a ranking of projects should not have duplicate values. The IT Manager/CIO should be specific and rank in a priority sequence aligned and agreed to within the organization; Project A=1, Project B=2, Project C=3, Project D=4, etc.

Thoughts?

This discussion is locked

All Comments