Gaps in the Overall Implementation Guide

From MIKE2 Methodology

Gaps in the Overall Implementation Guide provides an inventory of where the MIKE2.0 Overall Implementation Guide could be better extended to meet the needs of the proposed Solution Offerings are listed below.

Contents 1 Identified Gaps 2 Combining External Frameworks with MIKE2.0 3 Other Areas for Expansion 3.1 Activities in MIKE2.0 that Extend Beyond Information Development

Identified Gaps

Gaps in the overall approach are listed within each activity or in individual Solution Offerings. Activities where changes may occur are listed as Category:Potential New Activity or Category:Potential Activity Change. Proposed changes to Solution Offerings are listed within the offering.

Combining External Frameworks with MIKE2.0

As MIKE2.0 is specifically defined to build an Information Management competency that can be used with other methods or frameworks, there are areas where other approaches should be combined with MIKE2.0 to define a comprehensive solution. A brief overview of how this is applied by BearingPoint with its overall delivery framework is covered on the article Integrating MIKE2.0 to External Assets.

Other Areas for Expansion

Some activities that have not been considered to be explicitly in-scope for Information Management but may be added as part of a non-Information Development worksteam.

Activities in MIKE2.0 that Extend Beyond Information Development

A number of activities exist that overlap into areas of Application Development or Infrastructure Development. This include User Interface Design (application development) and Information Security Design and Infrastructure Management Process Design (infrastructure development).

Other activities being considered for addition include:

• Information Development Change Management - activities to support moving to a model of Information Development that relate specifically to cultural, process and organisational change

• Business Process Management - although some activities in MIKE2.0 provide a coverage of Information Management process, it may make sense to provide better coverage of this area by adding 1 - 2 more explicit activities.

• Business Modelling - tasks and techniques for building business models such as risk models based on the information that has been made available

Some existing activities such as Infrastructure Management Process Design may also be better extended as to support some Solution Offerings. It is possible that MIKE2.0 activities will be broken out into worksteams to better support this model.