Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

Members
Collapse Expand Close

To join, please contact us.

Improve MIKE 2.0
Collapse Expand Close
Need somewhere to start? How about the most wanted pages; or the pages we know need more work; or even the stub that somebody else has started, but hasn't been able to finish. Or create a ticket for any issues you have found.

Root Cause Analysis of Data Governance Issues

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Activities in Phase 3
Phase 3 - Information Management Roadmap and Foundation Activities
Content Model Relationship

Contents

Activity: Root Cause Analysis of Data Governance Issues

Objective

Preventing Data Governance issues involves analyzing those process activities or application automation that prevents Data Governance issues from occurring in the first place. Issue prevention is concerned with correcting root cause issues as opposed to addressing the symptoms. Issue prevention addresses Data Governance issues at the source systems, preventing poor quality information from flowing to downstream systems. It may also identify issues around security or architecture that will lead to Data Governance issues. Issue prevention is a key to reducing the excessive time that MIS staff spend massaging poor quality data.

Root cause issues that are identified as part of this activity should be tracked using the formal method established by the Data Governance team. This process will be revisited as part of the Continuous Improvement Activities conducted in Phase 5.

Major Deliverables

  • Root cause issues identified that lead to poor Data Governance
  • Recommendations for resolution of root cause issues

Tasks

Prevent Issues related to Source System Edits

Objective:

Many Data Governance issues stem from how data is captured and most typically result in poor data quality. Some of these problems can be addressed with additional training of users; technology changes such as screen validation, lookup values and basic business rules as part of the capture process can also prevent root cause issues. Stopping these issues from occurring on the front-end can prevent substantial downstream costs and should be the starting point for root cause analysis.


Input:

  • Tracking Mechanism for Data Governance programme issues
  • Enterprise Information Architecture
  • KDEs


Output:

Prevent Issues related to Business Process

Objective:

Poorly designed processes can result in Data Governance issues. Business Process problems can result in the same data being captured more than once, steps being done manually as opposed to automated, conflicting work efforts or poor calculation methods. Identifying the root causes of these issues and re-engineering business processes can have a major impact on improving overall Data Governance. The most significant improvements can often be made without technology changes.


Input:

  • Tracking Mechanism for Data Governance programme issues
  • Enterprise Information Architecture
  • KDEs
  • Current-state business processes and inventory of issues


Output:

Prevent Issues related to Technology Architecture

Objective:

Data Governance issues often stem from fundamental problems in the architecture or issues related to the complexity of the integrating information in a highly federated environment.

The most serious Data Governance problems can result from poor Data Governance practices related securing data. Latency issues that are inherit to integrating data between systems pose a major challenge in most organisations and result in the need to make major changes to the legacy architecture.

The results of the strategic current-state architectural assessment should act as valuable input into identifying these architectural issues at a strategic level and putting in place the strategic technology architecture for their resolution.


Input:

  • Tracking Mechanism for Data Governance programme issues
  • Enterprise Information Architecture
  • KDEs
  • Overall Blueprint Architecture


Output:

Summarise Root Cause Issues and Recommend Changes

Objective:

After Data Governance issues have been identified, it is time to define a programme of work for their resolution. Issues should be summarised and prioritised, based on the impact they have on in-scope KDEs. As addressing root cause changes may involve initiating another scope of work at this time and significant changes may need to be made to the plan.


Input:

  • Data Governance Issues related to Source System Edits
  • Data Governance Issues related to Business Process
  • Data Governance Issues related to Technology Architecture


Output:

Core Supporting Assets

Yellow Flags

  • Major issues identified for improvement in source systems or business processes, but there is not scope or funds to address these issues
  • Major architectural issues identified in the investigation process but there is not scope or funds to address these issuesthese issues

Key Resource Requirements

Potential Changes to this Activity

This activity may need to be expanded with 1 - 2 tasks that relate to unstructured content to have complete coverage for information governance.

Wiki Contributors
Collapse Expand Close