Building Making It Happen
Establishing Making-it-Happen as ‘Formal & Measurable’ Business Discipline
  Sign-in         Register
    
   Data Quality Approach Finalization Data Quality Policy  

Execution-MiH Encyclopedia  →   Enterprise Intelligence  →  SECTION -  Data Quality  →  CHAPTER -  Data Quality Program  → 

Data Quality Program Analyze Phase and Business case Closure

After the thinking process is over, its time to come out with a comprehensive proposal for implementing DQ program.

Firming up the business Case for Data Quality Program

This is toughie- Quantifying the business case for a Data Quality Program is somewhat similar to a profit & loss statement for an internal control OR audit OR Business Contingency Planning function. There is no fixed opinion on the impact of occurrence of an event OR its probability of occurrence.

Here are some methods one can deploy to bring it close to a typical revenue/cost initiative:

  • Leverage the findings of Data Mapping & Assessment.
  • Ask the business owners during DQ Program Analyze Phase- Approach Finalization to define the business case for ownership. A DQ program can only ride on the shoulders of business owners.
  • Using the audit & internal control findings as the basis.
  • Using regulatory exposure as the basis.
  • Conduct a quick study on the business impact in terms of head-counts, expenses and write-offs to set right the problems created by data quality. This will provide the ‘real monies’, which are getting wasted due to DQ issues.

Completing the ‘Analysis Phase’ of Data Quality Program

As stated before the analysis phase is the first stage, when one gets a high confidence quality program plan.

Typically a healthy estimate is expected at Data Quality Program Initiation. This works for projects (like implementing SAP, implementing a CRM initiative..) as which are related to something new and have similar implementations at other sites.

The Data quality program is mostly related to changes in the existing set-up and most of them not structural, but at the lower level of processes. Secondly, the changes needed are very specific to the given organization, and one cannot use a parallel to do a good estimation.

Therefore a Data Quality Program Initiation in a Data Quality Program will be mainly to get the sponsorship for the analysis phase. A high level approach and estimate of the entire program is definitely part of the project agreement (an outcome of the initiation phase), the stake-holders should be ready for a significant change post analysis, when they look at the analysis phase out-put, which will contain the following-

  • Detailed Data Quality Approach
  • Detailed Data Quality Plan
  • Business Case of Data Quality
  • Risks & Mitigation
  • Communication and Project Management Framework
 

   Data Quality Approach Finalization Data Quality Policy  
 
All Topics in: "Data Quality Program" Chapter
 Data Quality Program Initiation →  Data Quality Program DMA →  Data Quality Gaps Root Cause Analysis →  Data Quality Program Approach →  Data Quality Analysis considerations →  Data Quality Approach Finalization →  Data Quality Program Analyze Phase and Business case Closure →  Data Quality Policy →  Data Quality Organization Roles →  Data Quality Control Procedures → 
 

Was this page helpful?
If you like it ? share it !
Digg
Digg
Reddit
Reddit
Del.icio.us
Delicious
Google
Google
Live
Live
Facebook
Facebook
Slashdot
Slashdot
Netscape
Netscape
Technorati
Technorati
Stumbleupon
Stumbleupon
Spurl
Spurl
Furl
Furl
Blogmarks
Blogmarks
Yahoo
Yahoo
Plugim
Plugim
Squidoo
Squidoo
BlinkBits
BlinkBits
 
CONTENT ZONE
Data Quality

Featured Pages
Dimensional Model Simple Hierarchy
Data Warehouse Business Requirements
OLAP and Data Warehouse Dimensional Hierarchy
ROLAP- Relational OLAP architecture

Make 'Executable' Strategy
Maximize Results
Maximize People
Manage Execution

Featured Pages
OLAP Data Allocation Analysis
Pivoting, and Slicing & Dicing Analysis
Semi-Additive Measures-Facts
Physical Database Design and Implementation