 |
|||||||||
 |
 |
 |
 |
 |
|
||||
|
|||||||||
|
|
|
|
|
|
||||
|
|
|
|
| ||||||
|
|
|
||||
|
Great expectations: David Cox of Acuma argues that
business intelligence projects differ from other IT implementations and
demand a particular approach to risk management. |
||||||
|
Everyone who has been involved with IT projects
will know that such projects all share the same three objectives: Equally, experience of IT projects teaches that, very often, these objectives are not met. Business intelligence (BI) projects in particular have gained a reputation for being risky – the benefits don’t materialise as expected, arrive late and cost too much. The primary reason for this is that BI can’t be implemented as just another IT project. It has some special characteristics that are easy to overlook. This introduces an element of risk that is often inappropriately managed. In this article I aim to highlight some of these special characteristics, examine why they introduce extra risk and suggest best practice and techniques for managing this risk. Why BI is different. BI solutions can never exist in isolation. They are always dependent on other systems for raw data. Data quality issues lurking in those systems will be relentlessly exposed during a BI project and they must be addressed if users are to get accurate, comprehensive, reliable, up-to-date information. |
||||||
|
International Consultants' Guide May 2001
|
||||||
Data
Warehousing & Business Intelligence 
They must deliver
the expected benefits.