posted 11-06-1998 5:03 PM CT (US)     

Posted Question:

I conduct regular reviews of MIS project priorities with various user departments. We meet regularly and go over the projects and discuss. Now it comes time to decide in what order to tackle them.

What is the current best practice method for prioritizing projects. I'm trying to develop a consistent and logical method.

1) Squeaky wheel?
2) Business Value?
3) Based on business objectives?
4) Weakness link in the overall system?
5) Take a vote?
6) Lastest business issue?
7) First in/First Out?
8) Last in/First

Are they any white papers of best practices written about this subject?

And if there is no consensus, who ultimately should make the final call?

----------------

My Response:

At least you have regular reviews with your user departments!

At my company we conduct monthly steering committee meetings which include:

President, VP Administration, VP Marketing, VP Sales & Service, Director of Materials, Director of IS, VP Accounting.

This group has the utimate say in the order which projects are undertaken. It is not always easy, but at least we all end up in agreement. To cover your questions:

1) Squeaky Wheel

Sometimes this gets the resources because it represents a true business need. Usually this
need is obvious to the group.

2) Business Value

We try to make this our top concern.

3) Business Objectives

We are always looking out one to two years and we are attempting to match our project schedules to our strategic plans (new products, business expansions, etc.). This is our highest criteria for approval of a project.

4) Weakness Link

Usually this surfaces as a squeaky wheel (#1).

5) Vote

I have not seen this done yet - disagreements are fully discussed then they are either tabled to the next meeting or decided by our President.

6) Latest Business Issue

These discussions usually result in the group asking IS to come back with a project recommendation (if required).

7) First In/First Out

This would never fly given the competition for scarce IS resources.

8) Last In/First Out

Same answer as above.

My conclusion over the years is that sound business decision making by the key corporate or divisional executives is the best practice. Of course this may require homework on the part of the IT Department - project costs, scheduling, ROI, etc. In our case, the master project list is maintained and presented by the IT Group.

I would be interested in seeing how other organizations are doing this --