Business Intelligence Projects: Why They Fail (Part 1 of 5) - The Crumbling Foundation
For Business Intelligence projects (BI) to be successful, they must meet user requirements, be designed with strong user involvement, include a manageable scope, provide fast query response times, deliver the required reporting and analytic capabilities and provide value. Also, as nearly all experienced BI practitioners will attest, for business intelligence projects/programs to be successful, they must be built iteratively. In the trenches, that means sourcing, integrating, and developing front-end capabilities that target a subset of the enterprise data in each project. Sometimes the scope of an integration project is limited to a specific organizational process, such as invoicing, and other times by system, such as order-to-cash. Either way, subsequent business intelligence projects add to the scope and volume of data that is integrated and available for analysis. For initial business intelligence projects and subsequent iterations to be successful, the data architecture must be scalable, flexible, understandable and maintainable. However, most organizations put more thought and effort into their selection of BI tools than their data architecture. The end result is that they implement a data architecture that crumbles under the growing requirements of their users and data.