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.

MIKE2:Future Requirements

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Mike2 logo.jpg
Future Requirements This page provides you with an area to put forward a set of proposed requirements for a future release. Requirements put forward in this section should be done in a more structured fashion than in the Idea Lab. This section will eventually be moved to a community forum area.


Listed below are some of the key requirements identified for future releases of MIKE2.0 identified by the MIKE2.0 Leadership Team. This list will soon be moved into a more user-friendly table format, where each issue will include:

  • Component area
  • Requirement
  • Requirement description
  • Impact area
  • Importance
  • Additional comments on planned resolution

The Sortable Tables Extension will be used for storing this content.

Contents

Open Requirements

Create Case Studies for MIKE2.0

Develop MIKE2 Case Studies using existing qualifications as a starting point. Some of the key Case Studies can be loaded up onto the MIKE2 wiki and extended to tell more of a story around the value of an Information Development approach.

Compile Supporting Statistics for Information Development Approach

The MIKE2.0 Methodology proposes an Information Development approach as a best practice. This proposed approach should be supported by hard facts on areas such as:

  • IT spend on information development vs. application development
  • Financial benefits of centralised organisational models
  • Spend on data quality
  • Spend on business problems such as SOX and Basel II
  • Benefits around Customer Insight, Supply Chain, etc

In summary, this should be an inventory of information to support the Executive Summary and Business Case for Information Development.

Complete Priority "Wanted Pages"

There are a number of "redlinks" in the MIKE2.0 Wiki, which are pages that have been linked to but do not exist yet. Some of these wanted pages should be built before the initial release of MIKE2.0, whereas others can be populated after the first release. Redlinks should be reviewed and priortised.

Create MIKE2.0 Article on Wikipedia

Once MIKE2.0has been public for some time, create an article on Wikipedia that introduces the open source methodology. This will help attract users to MIKE2.0.

Add Content to Each Input and Output

Should add link in every input and output out of the tasks in the Overall Implementation Guide and describe each one of these links. Ideally these links will be described in detail through Deliverable Templates or sample Supporting Assets. They be described at least a high level. Using this approach with common names for inputs and outputs, "what links here" can be run to determine the exact dependency of each deliverable.

Improve Linking Across Wiki Content

The wiki should be reviewed and more linking should be added across wiki pages, following standards put forward in the MIKE2 Style Guide.

Investigate Options for Editable Image Formats

Right now, all images in MIKE2 have been created using powerpoint or visio and then converted to JPEGs, GIFs or PNGs using the GIMP image program. This means that these image formats cannot be edited from the commons. It should be investigated whether other image formats could be used that all users could edit from the original.

Build Tool to Track Activity and Task Dependencies

A tool should be built that draws out a graphical display of input/output dependicies of MIKE2.0 tasks. This tool could read content from the wiki db and render content on the screen as a project management tool - showing MS-project style dependencies. Existing plugins to MediaWiki should be investigated to see if any would be helpful. This would greatly improve usability in MIKE2.0

Complete Priority Deliverable Templates

Many users would like to see MIKE2.0 offer more "output templates". A priority list should be created for these templates and some additional templates can be created for the methodology.

Create QuickScan Assessment Model for Open Source Technologies

We should develop an Open Source Maturity Model and QuickScan tool that complements our other assessment models such as IM QuickScan and Vendor QuickScan. This model should also use a 5-level approach that is similar to IM QuickScan and be done within a web-based tool.

Add New Baseline Questions to Information Maturity QuickScan

The current version of Information Maturity QuickScan provides a baseline set of 175 questions that can be extended/changed as needed. These questions are somewhat weighted towards Data Quailty Management, these questions should be reviewed and extended over time.

Extend Technology Selection QuickScan

Review and extended Vendor QuickScan to cover other technology areas. It currently covers:

  • Data Investigation and Re-Engineering
  • ETL Integration
  • Metadata Management

This could be extended to include other areas, such as:

  • Business Intelligence
  • Database Management
  • Data Models (coverage for certain data areas)
  • Data Modelling tools
  • Configuration Management tools
  • BRE (Business Rule Engines)
  • Business Process Management
  • Web Portals
  • Unstructured Data Management

The goal is to have quick assessment model for any type of technology that may be selected in Phase 2 of MIKE2.

Develop Open Source Maturity Model

Develop an assessment model that can be loaded into the overall web-based assessment framework and is conducted during the Organisational QuickScan Activity of MIKE2.0. This QuickScan defines a 5-level maturity model (similar to the one used for IM QuickScan) that can be used to judged an organisation's maturity level regarding Open Source (from "Aware" to "Optimal").

This assessment would be complemented by the Technology Assessment QuickScan.

Develop Process for Using MIKE2.0 to Drive Open Source Software for Information Development

One of the main goals of the MIKE2.0 Methodology is to provide an "organising framework" for open source technologies in the information development space. There are a growing number of open source projects in this space, but there are also some gaps where MIKE2.0 can help out around open source software development:

  • Review articles against open source projects, using a standard template
  • Use of Technology Assessment QuickScan to review Open Source projects
  • Definition of new requirements for open source projects (Technology Assessment QuickScan) can help provide a starter set of high level requirements
  • Assignment of staff to look for new open source initiatives and help drive them to completion (acting in various project roles)
  • Contribution of our own content (e.g. MIKE2.0 methodology, vETL, metadata model) to the open source community

MIKE2.0 is not seen as the environment to host open source projects (i.e. it will not try and act as a replacement to SourceForge), but a way of bringing this together through reviews, linking it into an overall approach and helping to drive projects to completion.

Create SAFE Open Source Architecture

Provide initial SAFE architecture framework based solely on Open Source technologies. This will be part of the overall MIKE2.0 Solution for Open Source.

Create Webinar - Overview of the MIKE2.0 Methodology

Driven via front-page (for beginners, for users, for contributors), covering the following in this 30 - 60 minute webinar:

  • What is MIKE2.0?
  • Why did we create MIKE2.0?
  • What is the DGMC?
  • Why did we Open Source MIKE2.0?
  • A brief overview each aspect of MIKE2.0, driven from the overall content model
  • What can be found in the other MIKE2.0 webinars?

Create Webinar - An Introduction to MIKE2.0 Concepts

Topics covered in this 30 - 60 minute webinar:

  • Enterprise Views and how it changes the approach to Application Development and Infrastructure Development
  • Information Development
  • XBR
  • SAFE
  • Building a Centre of Excellence
  • Continuous Communication through Blueprinting
  • Continuous Implementation through repeating increments
  • Continuous Improvement

Create Webinar - MIKE2.0 Overall Implementation Guide

Topics covered in this 30 - 60 minute webinar:

  • Purpose of the Overall Implementation Guide
  • Contents of an Activity
    • Deliverables
    • Tasks
    • Inputs/Outputs
    • Core Supporting Assets
    • Yellow Flags
    • Key Resource Requirements
  • Activity Walkthrough: High Level Information Requirements
  • Activity Walkthrough: Solution Architecture Prototype
  • Activity Walkthrough: Continuous Data Quality Improvement
  • Talk Pages for Activities
  • Release Cycle for the Overall Implementation Guide

Create Webinar - MIKE2.0 Solutions

Topics covered in this 30 - 60 minute webinar:

  • Purpose of MIKE2.0 Solutions
  • Overall set of Solutions
  • Solution Overview - Data Investigation and Re-Engineering
  • Solution Overview - ETL Integration
  • Solution Overview - Data Governance and the Information Development COE
  • Plans for Future Solutions

Create Webinar - MIKE2.0 Supporting Assets

Topics covered in this 30 - 60 minute webinar:

  • Purpose of Supporting Assets
  • Different Types of Supporting Assets
  • Supporting Asset Walkthrough: IM QuickScan
  • Supporting Asset Walkthrough: Economic Value of Information Calculator
  • Supporting Asset Walkthrough: Data Profiling Design Patterns
  • How Supporting Assets are used to extend/exchange MIKE2.0
  • Contributing to the library of Supporting Assets

Create Webinar - Contributing to MIKE2.0

Topics covered in this 30 webinar:

  • Licensing model overview
  • Rights/responsibilities as a user
  • Rights/responsibilities as a contributor
  • How to add contents to MIKE2.0 following the contribution model (stubs, peer reviews)
  • The MIKE2.0Release Cycle

Create Webinar - MIKE2.0 Usability

Topics covered in this 30 - 60 minute webinar:

  • How to use navigate the web-based version of MIKE2.0
  • Spell checking with Google toolbar

This webinar is giving users a better experience to using a fully web-based methodolog

Provide additional detail on using MIKE2.0 with other methods

Provide a more detailed, solution-oriented approach for intergrating MIKE2.0 into approaches such as TOGAF, Zachman or Six Sigma

Create Model for a "Custom" Version of MIKE2.0

Organisations may want to use MIKE2.0 by taking a baseline release and implementing it into their own environment. This means that they would receive an export of MIKE2.0 wiki db at a point in time and would create their own branch in the release. Clients may also want other aspects of the overall collaboration environment. This can easily be done by providing available extract files and list of software to be installed.

Create Open Source Web-Based Assessment Infrastructure

BearingPoint has a web-based assessment framework that we can use to migrate in existing QuickScan tools. Over the long-term, the goal is to have an Open Source Assessment Framework as part of MIKE2.0.

Create DGMC User Directory

There should also be a user directory for Data Governance Consortium members that contains personal/contact information. This can be stored in each user's detail page - but it must be clear who is part of the DGMC and how they became a member

Add a mechanism for users to vote on articles

Contributors on MIKE2.0 should be able to vote on each article, to rate the following:

  • Relevance to the problem they are facing
  • Quality of the article

Create Vendor-Specific Technique Papers

Currently, there are only a few sample vendor-specific Supporting Assets. Will focus on adding more vendor assets and commercial vendors are encouraged to add their own assets.

Simplify Dependency Model

Make it easier for a user to understand flow of activities by showing a graphical view that users can navigate

Simplify Dependency Model

For contributors, make it easier to understand what is protected and where they can most effectively contribute. Articles exist, but it should be made more easy to see through tooltips or htmlets.

Recently Completed

The text below may not reflect current status, but refer to the initial requirement. All of these requirements are viewed as closed in the article may still be in the process of being edited, but it is now at the point where it is at a reasonably mature state.

Create Master Data Management Solution

MIKE2.0 Solution for MDM has not yet been created, but there is already content that can be used to build a "under construction" solution.. The MIKE2.0 Solution for MDM should bring together Supporting Assets that include: Existing content (all at a very high level, more detail should be added)

  • What is MDM and what are the key data management issues associated with it
  • How does MIKE2.0 relate to MDM
  • What aspects of the SAFE architecture are most important for MDM

None of this content is in the wiki yet but is already in MIKE2 for MDM Overview

Other content to add:

  • Required Activities from MIKE2.0 for MDM
  • High Level Solution Architecture Options
  • Pro/cons of High-Level Solution Architecture options
  • Differences between different vendor approaches
  • Vendor-specific implementation techniques

Create Data Modelling Solution

An initial draft has been created of the MIKE2 Data Modelling Solution. This content has also been added to the wiki. Improvements to be made include defining a more process-centric approach for data modelling.

Create Data Governance Solution

A Solution for Data Governance has been created under the name Information Development Centre of Excellence. This content was originally in the COE Solution Guide and also in a word document for Data Governance. Improvements to be made to this solution include:

  • Consistency in terminology around Data Governance and Information Development
  • Additional wording around maturity models
  • Add in redlinked resources
  • Peer Review revise existing definition for resources and see if they are clear

Create Business Intelligence Solution

This Solution will reference most Activities of the Overall Implementation Guide. Should also reference activities such as Data Investigation and Re-Engineering, Data Modelling and Metadata Management

The solution will focus on bringing in content around warehouse architecture. Some of this content exists as high level Solution Architecture options around:

  • Overall Data Warehouse Architecture
  • Security Architecture
  • Centralized vs. De-Centralized approach

Should Peer Review this approach for internal pilot and try and gain additional contributors

Create IT Transformation Solution

The MIKE2.0 IT Transformation Solution will reference most Activities of the Overall Implementation Guide. The Solution will focus on why a data-driven approach is critical to Transformation and how SAFE and XBR are critical aspects of an overall Transformation programme. This Solution should be focused on bringing together the following areas:

  • Guiding Principles for the Technology Backplane
  • How to align programmes around Data Migration and Data Warehousing as part of an overall Transformation
  • The importance of getting Technology Backplane capabilities "out front" as part of a Transformation
  • Model for aligning Application Development to Infrastructure and Information Development
  • Organisational model for IT Transformation (using the Information Development team organisational model)

None of this content is currently in the wiki but it all exists in overview presentations at an appropriate level to get an "under construction" solution.

Create Information Management Strategy Solution

This Solution should discuss the Activities for building an Information Management Strategy through either a ""Top -Down"" or ""Bottom-Up"" approach.

  • Top-Down: The first 2 phases of MIKE2.0
  • Bottom-Up: Start with Data Investigation (IM QuickScan, then Data Profiling). The bottom-up approach is largely the approach followed in the Data Investigation Solution.

All this content already exists in other articles, just needs to be brought together in a short solution.

Create Data Migration Solution

MIKE2 Solution for Data Migration has not yet been created, but there is already content that can be used to build a "under construction" solution. The MIKE2.0 Solution for Data Migration should bring together Supporting Assets that include: Existing content:

  • Guiding Principles for Data Migration
  • Traditional Data Migration high-level solution architecture
  • Application Co-Existence high-level solution architecture
  • Estimating factors for a Data Migration programme

None of this content is in the wiki yet but is already in the SAFE architecture.ppt

Other content to add:

  • Required Activities from MIKE2.0
  • Pro/cons of high-level solution architecture options
  • Detailed implementation technique supporting assets
  • Vendor-specific implementation techniques (on the integration side and for specific source-target applications)
Wiki Contributors
Collapse Expand Close