MIKE2.0 methodology

From Wikipedia, the free encyclopedia
(Redirected from MIKE2.0 Methodology)

The Method for an Integrated Knowledge Environment (MIKE2.0) is an open source delivery methodology for enterprise information management consultants. MIKE2.0 was released in December 2006 by BearingPoint's Information Management team under the leadership of Robert Hillard. The project used Creative Commons Attribution License and was implemented by Sean McClowry. The project is now run by the MIKE2.0 Governance Association,[1] a non-profit organisation based in Switzerland, with BearingPoint and Deloitte as the founding members. In March 2013 a book Information Development Using MIKE2.0 was published promoting it.[2]

Description[edit]

The methodology provides a framework for information management. It covers how information is created, accessed, presented and used in decision-making to how it is kept secure, stored and destroyed.

Information development[edit]

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[edit]

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.

Open methodology framework[edit]

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]

Content model[edit]

MIKE2.0 Content Model

MIKE2.0 is made up of building blocks, given in a block diagram.

Products[edit]

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[edit]

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[edit]

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.

Overall task list[edit]

  • 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[edit]

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.

Collaboration environment[edit]

The MIKE2.0 Methodology

The MIKE2.0 collaboration environment is provided through omCollab, an open source collaboration product that provides the following capabilities:

  • A Wiki to collaboratively create and share content (based on the same MediaWiki software that powers Wikipedia)
  • Blogs to publish individual or group-based information (based on WordPress)
  • Social Bookmarking for storing, sharing and discovering web bookmarks
  • Social Networking for the MIKE2.0 community to store basic profile information and to interact with one another.
  • Tag (metadata) and categories are used to classify articles, blogs and bookmarks into a common taxonomy. MIKE2.0 brings these two concepts together in the bookmarking component.
  • Techniques and technologies to mashup to MIKE2.0, to build integrated solutions based on open content and internally held assets
  • Search for users to discover content across federated repositories. MIKE2.0 uses Google Custom Search.
  • A rich user interface with advanced navigational components an integrated skin and single sign on to provide common look and feel across the platform
  • An open methodology compliance (OMC) capability to link an organisation into MIKE2.0

The overall product is referred to as "omCollab" and was released in 2008.[8]

Impact[edit]

Since its release, MIKE2.0 was referenced as a case study on Web 2.0 reports,[9][10] The 2008 book Groundswell used MIKE2.0 as a case study. The content was taught through online webinars and as a part of a Melbourne University lecture series on data warehousing in 2008.[11] The Association for Information and Image Management (AIIM) included a case study of MIKE2.0 in their Enterprise 2.0 specialist certification program in 2008.[12]

Criticisms of the approach[edit]

References[edit]

  1. ^ "MIKE2.0 Governance Association". www.openmethodology.org. Retrieved 2009-07-07.
  2. ^ "MGA Book Release Announcement: "Information Development Using MIKE2.0"". Press release. April 16, 2013. Retrieved April 3, 2017.
  3. ^ Interview with Robert Hillard. "Simplifying the methodology of Information Management". podtech.net.
  4. ^ Interview with Sean McClowry. "What is MIKE2.0". Data Migration Pro.
  5. ^ "Integrated Content Repository Overview from MIKE2.0". www.openmethodology.org. Retrieved 2008-05-05.
  6. ^ "Open Methodology Framework Overview from MIKE2.0". Openmethodology.org. Retrieved April 3, 2017.
  7. ^ "MIKE2.0 view on likely alternatives to current release mode". www.openmethodology.org. Retrieved 2008-05-05.
  8. ^ Andreas Rindler (July 11, 2008). "omCollab contribution to the open source community". MIKE2.0 blog. Retrieved April 3, 2017.
  9. ^ Michael Gerard, Seth Fishbein. "IDC CMO Advisory Best Practices Series: B-to-B Online and Interactive Marketing ... Cutting Through the Hype". IDC Research. Archived from the original on 2010-03-13. Retrieved 2008-01-01.
  10. ^ Anant Jhingran. "Information Management Communities". Retrieved 2008-05-05.
  11. ^ "Melbourne university course on Data Warehousing". Melbourne University. Archived from the original on 2008-04-12. Retrieved 2008-05-05.
  12. ^ "AIIM Enterprise 2.0 Specialist Program" (PDF). AIIM. August 15, 2008. Archived from the original (PDF) on March 4, 2009. Retrieved April 3, 2017.

External links[edit]

Retrieved from "https://en.wikipedia.org/w/index.php?title=MIKE2.0_methodology&oldid=1074476102"