The Answer

This article is Part III of a series of three articles outlining the pitfalls of implementing systems projects, and ultimately, how to avoid them. In Part III, Business Improvement Consultant Anne MacLeod identifies some of the root causes of IT system project failures and the challenges to address them.

Part I  |  Part II  |  Part III

You are probably aware that IT is essential to your corporate survival. There is no lack of information from software companies, consultants, and other "experts" knocking on your door, all offering the "best" solution for your business.

On the other hand, you've heard the horror stories: Cost overruns, late projects, faulty vendors, dissatisfied users and customers - and the list goes on. The first two articles in this series explored the perception and realities of IT project mistakes. The question is, how can companies prevent these mistakes from happening before the implementation stage?

It's all in the planning.

In our experience, we've found that:

• systems projects require Project Management disciplines in order to succeed
  
  
• systems projects require intimate business process knowledge in order to identify the right problems and solutions

Project Management

As the saying goes "You can't play baseball without touching all the bases." The same is true for IT projects. It is critical for organizations to utilize Project Management disciplines when implementing large and small systems projects. The basic steps are:

• Project Charters
  
  
• Business Plans
  
  
• Launch Proposal (Project Plan)
  
  
• Sanity Check (often referred to as Go/No go)

All parts of the organization are involved in these steps. Key roles are:

• Executive sponsorship - for charters, prioritization of projects and resource assignment (capital and operating)
  
  
• Business client involvement - for all aspects of the project including business plans (cases) and ultimate acceptance of the solution
  
  
• Project Managers, IT professionals and vendors - for development and delivery aspects of the project.

Business Process Knowledge

There are some key aspects to ensuring that business processes and technology address the same issue:

• Approaching systems projects from a business aspect rather than a purely technical aspect
  
  
• Identifying the baseline process
  
  
• Identifying measures of success and goals for improvement

Starting a project with business process mapping often highlights other aspects of the business that must change prior to implementing technology. Sometimes, the answer lies in changing the business process itself, before technology is brought into the picture at all.

This allows the business to:

• address organization/resource issues associated with change
  
  
• supply measures of success for systems projects by establishing baseline metrics and targets for improvement
  
  
• properly scope applications and technology, ensuring that all aspects of the project are addressed and tested adequately with the change
  
  
• address project cost and time constraints

Mandating the right project, with the right resources, right processes, and technology will ensure your IT project's success. Proper planning ensures that your company will get it right the first time.

Part I  |  Part II  |  Part III