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

Collapse Expand Close

To join, please contact us.

In other languages
Collapse Expand Close
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.

Overall Implementation Guide Overview

From MIKE2.0 Methodology

Jump to: navigation, search

MIKE2.0 Content Model

The Overall Implementation Guide collates all of the content contained within MIKE2.0 framework. In a nutshell, the guide is the organizing framework for bringing everything together. The Overall Implementation Guide is comprised of the following:

  • Overview and Key Concepts introduces users to a new set of enterprise models and the concept of Information Development. The latter is especially important, as it is used extensively throughout the MIKE2.0 Methodology. It helps users understand the benefits of superior information management.
  • The section on Rationale details the development of the MIKE2.0 approach. It further details why the solution was created and a bit of the history on how it took its current form.
  • The 5 Phases of MIKE2 outline how MIKE2.0 has adopted an iterative, agile approach for continuous implementation. This approach divides the development and rollout of an entire system into a series of implementation cycles.
  • The Overall Task List provides the overall set of Phases, Activities, and Tasks for MIKE2.0.
  • The Usage Model provides some guidance on how these tasks are applied to different types of projects.

To better appreciate the activities and tasks of the Overall Implementation Guide, it is useful to describe the architecture framework and delivery model at a high level. This includes:

  • Information Governance Solution Offering. This helps users understand the skills that will be required on the team, how tasks are to be structured, and some of the guiding principles around the MIKE2.0 delivery approach.

Note that the development of the methodology is a continuous process. To this end, MIKE2.0 has been constructed in a fashion that allows functionality to be added underneath the Overall Implementation Guide and governing architecture.

MIKE2.0 Task Model

The Overall Implementation Guide provides the governing set of Phases, Activities, and Tasks for the MIKE2.0 Methodology:

  • Phases are the major lifecycles of a programme. The MIKE2.0 Methodology has five phases as part of its continuous implementation approach.
  • Activities describe major units of work through a focus on key concepts and deliverables.
  • Tasks describe the detailed set of steps within an Activity that are required to produce the overall set of deliverables.

Each Phase, Activity, and Task consist of the following:

  • Objective - an overview of the particular step
  • Input - dependencies to initiating the particular step in the process
  • Deliverables/Output - describe the ultimate work or item created via this step in the process

At the Activity level, the following are also defined:

  • Core Supporting Assets - references to Key Supporting Assets (KSAs). Only Public Supporting Assets are listed within the Overall Implementation Guide. A number of other KSAs are linked into the methodology through either internal knowledge management systems (internal version) or through categories in the open methodology.
  • Yellow Flags - issues that typically cause problems--or at least pose the risk of doing so.
  • Key Resources - typical types of resources needed to perform an activity. Note that this key resources reflect high-level models. For more detailed analysis and work, users should employ MIKE2.0 estimating tools for more accurately results.

Each of these areas will be enhanced over time. Doing so supplement the core methodology. Contributors to MIKE2.0 can recommend extensions and new Core Supporting Assets to the Overall Implementation Guide.

When undertaking a project, users of the MIKE2.0 Methodology are best served as follows: 

  • start with this Overall Implementation Guide
  • look at the MIKE2.0 Usage Model
  • then use the more detailed assets
Wiki Contributors
Collapse Expand Close

View more contributors