How to leverage agile BI to help your BI architecture

How can we leverage agile business intelligence (BI) to help with our BI architecture?

    Requires Free Membership to View

    Login

    When you register, you'll receive targeted emails designed to keep you informed of the latest BI, analytics, corporate performance management (CPM) trends and more.

    Hannah Smalltree, Editorial Director

    By submitting your registration information to SearchBusinessAnalytics.com you agree to receive email communications from TechTarget and TechTarget partners. We encourage you to read our Privacy Policy which contains important disclosures about how we collect and use your registration and other information. If you reside outside of the United States, by submitting this registration information you consent to having your personal data transferred to and processed in the United States. Your use of SearchBusinessAnalytics.com is governed by our Terms of Use. You may contact us at webmaster@TechTarget.com.

You should logically split your BI architecture into two categories: data integration processes and BI applications. To be most successful, an enterprise should then manage the design, development and deployment of those two categories differently.

Data integration involves processes such as gathering business and data requirements, data modeling, data profiling, cleansing and conforming data, and creating extract, transform and load (ETL) routines. Although an enterprise should follow an incremental and iterative approach to that work, data integration involving more than one data source and business group typically doesn’t lend itself to a formal agile approach.

Agile techniques are a great way to foster development of BI applications, such as dashboards, scorecards, reports and analytics applications. This is especially true when the data is already in place and the initial set of business requirements has been defined and prioritized. At that point, quick development (or prototyping) of reports, analytics and dashboards enables IT developers to show business users what they’re building and quickly gather feedback on the designs. Agile BI techniques can significantly reduce the likelihood that IT will develop something the business cannot use. In addition, it’s very common for business users to refine requirements or identify new ones that they forgot about or assumed that the IT staff knew about. An agile approach can make it easier to accommodate such changes.

The key management issue is to timebox the development tasks for each BI application. Otherwise, the project can get into an agile paralysis loop (similar to analysis paralysis, only in the development process.)

This was first published in January 2011

Join the conversationComment

Share
Comments

    Results

    Contribute to the conversation

    All fields are required. Comments will appear at the bottom of the article.
    Back to top