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.

Enterprise Information Management Awareness

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Content Model Relationship

Contents

Activity: Enterprise Information Management Awareness

Objective. The objective of the Enterprise Information Management Awareness activity is to educate the participants organisation on the subject of Enterprise Information Management before focusing in on their specific problem area (e.g. Data Warehousing). This is done to ensure that staff understands basic terminology, the different architectures, and the capabilities and limitations of the proposed solution.

This activity should help set the level of understanding prior to launching forward with the project. The organisation should also understand its primary informational requirements, at least at an overview level.

As there is much material to cover, this activity may take multiple sessions. It may be helpful to iterate through presenting the "big picture" view and the potential information management solution that is more specific to the clients’ needs. For some projects, the scope may be quite undefined, hence the need to present the complete story in this area.

Upon completion of this activity, the three primary audiences should be able to articulate, at a minimum, the following:

  • Basic concepts in information management
  • How it relates to their business problem
  • Their role in contributing to a successful initiative for the programme

Staff should be advised that education on Enterprise Information Management principles will be an ongoing activity and they need not worry if they don’t understand all the concepts right away.

Major Deliverables


Common assets:

Tasks

Task: Assess Team’s Understanding of Information Management Concepts

Objective: In this task, the Executive Sponsor(s), the expected team members and the expected end-users ascertain their level of understanding of the key information management concepts and identify their expectations for the information management initiative through a set of meetings and interviews. These gatherings are not training classes, but rather informal conversations to allow the interviewees to express their beliefs and perceptions of the subject at hand. If the client is new to the subject, these conversations may be quite brief and interviewers should avoid pressing the client too much in the early stages of the project.


Input:


Output:

Task: Develop and Initiate Information Management Orientation

Objective: Develop initial set of training that will:

  • Close major gaps in the client’s understanding
  • Reset or confirm expectations
  • Begin to get an understanding of the key information areas that are in-scope
  • Identify the expected benefits of the project initiative

Often this training is the first time that the client’s key participants identified above have been exposed to key information management concepts. This initial training along with effective follow up will help to manage project expectations and establish and maintain the level of enthusiasm for the initiative.

Whereas the prior task is focused on the overall approach to information management, this task covers the scope that more closely aligns to what the client has stated as the project objectives. If the project scope is a Data Warehouse, for example, the training would cover:

  • Transactional vs. data warehouse structures and characteristics
  • Distinctions between data, information, and knowledge
  • Data warehouse architecture vs. transactional architectures
  • Data warehouse technical architecture components
  • The role of metadata
  • Role of Operational Data Stores in the informational environment
  • Data warehouse design considerations
  • Iterative nature of the data warehouse

Key concepts to introduce and explain these concepts are available in the MIKE2.0 Supporting Assets.


Input:


Output:

Role:Solution Architect

Role:XBR Process Manager

Yellow Flags

  • Major skill gaps on team in basic Information Management concepts
Wiki Contributors
Collapse Expand Close

View more contributors