MIKE2.0 methodology

While initially focused around structured data, it coined the term "information development". The MIKE2.0 approach is based on the premise that traditional software delivery has under-focused on the information management. The goal of MIKE2.0 is to create a new competency, specifically for managing information, [3] [4]

Integrated Content Repository of MIKE2.0

MIKE2.0 introduces the concept of an integrated content repository.[5]

This repository is a federated hub of shared assets from the Internet and content held internally within an organization. Using this concept, organizations can create mashups to the MIKE2.0 standard and information management assets on the World Wide Web. Although they are not required to share any of their assets with the open source community, they are encouraged to contribute. The content repository architecture is based on using wiki-pages created in MIKE2.0, assets that are linked from other sites using a social bookmarking tools and common tagging and extensions that allows users to create mashups into their organization.

MIKE2.0 claimed to be a pilot project for a "framework".[6] It proposes to be an approach which sits between a completely open Wikipedia-style model and a more rigorous development approach seen with software development. The collaborative technology, the structure of the content model and a number of content governance articles are used to enable this concept. The methodology states that this model is likely to evolve over time .[7]

Products tend to focus on a certain type of problem as opposed to being generalized for information management like the overall implementation guide.

SAFE Architecture for enterprise information management

The approach of the MIKE2 Methodology is to drive implementation of information management projects through a conceptual architecture framework known as strategic architecture for the federated enterprise (SAFE). SAFE goes across applications, data, and infrastructure and is designed to accommodate the inherent complexities of a highly federated organisation. Using a Conceptual Architecture helps align projects to a target vision for the future and to take the complexity out of the myriad of vendor choices around integration and information management.

Information governance is a term used in MIKE2.0. The governance model provides assessment tools, information standards, organizational structures and roles and responsibilities in relation to managing information assets. Governance 2.0 is another term used, along with Enterprise 2.0 techniques and technologies.

• Overview and Key Concepts frame the overall approach as well as the rationale for why MIKE2.0 was created.
• The overall task list is a project management and project implementation methodology consisting of five phases, activities for each phase, tasks for each activity and inputs/outputs for each task. These are:

• Phase 1 – Business Assessment and Strategy Definition Blueprint
• Phase 2 – Technology Assessment and Selection Blueprint
• Phase 3 – Information Management Roadmap and Foundation Activities
• Phase 4 – Design Increment
• Phase 5 – Incremental Development, Testing, Deployment and Improvement

The task list is underpinned by the information development approach and tightly integrated with SAFE architecture.

• Usage Models show how the different tasks are applied for different solutions. Usage models use an indicator approach to show the relevance of an activity.

Supporting assets complement the overall methodology with:

• Tools and technique papers
• Deliverable templates
• Capability statements
• Software assets
• Other tools and guides

Supporting Assets are typically the lowest-level assets of the overall approach.