Projects need prioritisation and monitoring

"Fix Martha's laptop" isn't in the same league as "implement CRM"

A most visible, and often cited, measure of the success of an IT department is the business success of the projects undertaken and the completion of those projects in a timely, cost-effective manner. Therefore, the successful selection, prioritisation, and execution of IT projects plays a large part in determining the overall success of the IT department. Selecting which, and how many, projects are allowed on the IT department schedule is a critical determinant of the overall success of those projects.

Project prioritisation is a complex process that involves identification of the different projects and assessment of the projects based on factors such as strategic value, financial value, risk, existing system adequacy, time to completion, as well as organisational capacity and technical complexity. These assessments are made to differentiate the high-priority projects on a project list based on relevant factors, particularly financial value. They are used to accurately reflect the priority of IT projects in supporting the business unit priorities — not IT’s self-mandated priorities.

Typically, a struggling IT department has dozens, even hundreds, of projects underway simultaneously. This is a common phenomenon that we have observed in organisations, regardless of size. The overall project inventory, if one exists, is littered with dozens of ill-defined, partially completed projects of indeterminate origin, benefits, goals and status. Compounding the issue is that the projects are scoped at wildly varying levels of complexity, size, and business impact, producing absurd results such as “fix Martha’s laptop” at the same level as “implement CRM”. Further, the project list has multiple dependencies (some identified, some not), internal inconsistencies, conflicting timelines, and unclear ownership on the part of both the business and the IT department.

In most cases, each of these projects is partially completed and in a perpetual state of being slowly shepherded to a fuzzy, indistinct and elusive finish line by the IT department, with little real hope of solid completion. Indeed, most IT departments have dozens, if not hundreds, of simultaneous projects, each being pushed forward infinitesimally each week. Because IT is attempting to work on multiple competing objectives, in many cases, the original rationale for the project has become obscured by the passage of time, personnel changes and changes in the business, often rendering the project irrelevant. Xeno’s paradox, which states that if you can achieve half the distance to the goal with each step, you will never arrive, comes to mind. The result of this common dilemma is an IT department that fails to complete, or even identify, the high-value, high-priority technology projects.

• This is an excerpt from The Executive’s Guide to Information Technology: 2nd Edition. The book, published by John Wiley & Sons, offers advice on how to improve IT delivery.

Join the newsletter!

Error: Please check your email address.

Tags managementprojectsprioritisation

Show Comments