Initiating a business intelligence program is unlike the launching of a traditional application development project. The most significant difference is due to the data (versus process) orientation of the effort and the importance of building a strong foundation that can accommodate change. Unlike processes, which are often aligned with organizational responsibilities, data frequently crosses organizational boundaries and doesn't carry with it a clear line of responsibility. For BI programs, this creates difficulties in determining succinct definitions, gaining consensus on business rules, establishing quality expectations, and determining access rights and permissible usage.  

Enterprises contemplating a BI program should assess their readiness to move forward and create a charter for the overall program.

Register or login for access to this item and much more

All Information Management content is archived after seven days.

Community members receive:
  • All recent and archived articles
  • Conference offers and updates
  • A full menu of enewsletter options
  • Web seminars, white papers, ebooks

Don't have an account? Register for Free Unlimited Access