MIKE2.0 Method: An Open‑Source Approach to Information Development

MIKE2.0 Method: An Open‑Source Approach to Information Development

What is MIKE2.0?

MIKE stands for Method for an Integrated Knowledge Environment .

MIKE2.0 is the comprehensive enterprise information management methodology.

It incorporates key concepts from open source and Web 2.0.

The open‑source version is available at http://www.openmethodologology.org .

Key Structures in MIKE2.0

SAFE (Strategic Architecture for the Federated Enterprise) – the future‑oriented framework.

Information Development – the core concept, treating information as a product to be developed like software.

MIKE2.0 Provides a Comprehensive Modern Approach

Covers the full scope of enterprise information management while detailing tactical project areas.

Starts with a strategy‑level, architecture‑driven method and progresses to solution architecture.

Encompasses data governance, architecture, and strategic information management.

A Collaborative Open‑Source Method for Information Development

Balances adding new content with stable releases through an easy‑to‑navigate method.

Allows contributions from non‑technical users.

Aims to become the "standard" for new information‑development domains.

MIKE2.0 Method: Phase Overview – The Five Phases

Phase 1: Business Assessment

Phase 2: Technical Assessment

Phase 3: First Iteration

Roadmap and core activities → Design → Development → Deployment → Operations

Phase 4: Second Iteration

Roadmap and core activities → Design → Development → Deployment → Operations

Phase 5: Third Iteration

Roadmap and core activities → Design → Development → Deployment → Operations

MIKE2.0 Method: EDM Strategy Activities and Typical Timeframes

MIKE2.0 Task Overview – Task 1.4.3 Assess Information Maturity

The following shows a sample output of the Information Maturity (IM) QuickScan, used as the first step to assess data‑governance levels in an enterprise‑wide organization.

MIKE2.0 Task Overview – Task 1.5.10 Advanced Solution Architecture Options

The example below displays possible advanced solution‑architecture options that will be used for this task; typically, several models are presented with supporting text.

This proposed solution includes three viable choices:

Use a vendor model as the logical data model for integrated operational data storage, refined through map‑gap exercises; it aligns closely with the organization’s existing data classification model.

Develop and build a hybrid data model composed of existing data models from internal systems; these base models must be supplemented and integrated with other models used by enterprise applications.

Based on the already‑adopted organization‑wide classification model and clear user requirements, internally develop a logical, normalized data model that supports the required functionality.

Defining advanced solution architecture is only part of the overall architecture approach.

If an initial assessment of current state and vision is needed, modify the overall architecture model.

Define guiding principles.

Create a strategic concept architecture.

Define advanced solution‑architecture options.

Collect strategic requirements for integration and information.

Define logical architecture to understand required product functions.

Map logical architecture to physical architecture to select vendors.

Gather detailed business requirements.

Define/revise solution architecture.

Define technical and implementation architecture.

Strategic business and technical architecture activities are performed once; more detailed activities are executed for each delivery increment.

Task Overview – Define Infrastructure Baseline Functions (Task 2.2.2)

The following shows a sample output from the QuickScan Technical model, a simple model that can serve as a starting point for defining strategic capabilities across technology backbones, later used in vendor selection (Activity 2.6).

Task Overview – Define Capability Deployment Timeline (Task 2.11.3)

Defining EDM Strategy – Lessons Learned

Define an executable strategy

If needed, launch a large‑scale top‑down and bottom‑up strategy (narrow and detailed).

Focus on quick‑win, high‑ROI activities such as data quality and metadata management.

Always define tactical, strategic, refactoring, and continuous‑improvement plans throughout the project lifecycle.

Design a strategy that is both flexible and meaningful for the enterprise

Anticipate changing business requirements – provide infrastructure to handle dynamic business.

Identify risk areas for each incremental implementation – focus on foundational activities.

Beware of technology lock‑in and understand exit costs – adopt an open approach.

Break through legacy technology constraints – an opportunity to drive change.

Engage the business

Prioritize technical backbone capabilities while designing strategy to deliver meaningful business value from day one.

Continuously communicate the plan defined in the strategy – the overall blueprint serves as the lifecycle communication document.

Work closely with users to understand data value, not just system functionality – design a truly data‑centric approach.