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.

Composite Solution Offering Creation Guide

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search

This article provides a guide for creating MIKE2.0 Composite Solution Offerings. It shows how the Solution Offering maps into the Solution Capabilities of the overall MIKE2.0 methodology as well as into other Solution Offerings on the open methodology site.

Contents

Introduction

Overall Instructions for the Creation Guide
The purpose of a Solution Offering is to:
  • Describe the Solution Offering and show its relationship to other offerings
  • Map the Solution Offering to the Key Elements of the overall open methodology site
  • Assets mapped into the Suite can be open, shared or private assets

Executive Summary

Instructions
Provide a brief overview and scope of the Solution Offering. Summarize in a few sentences the differentiating features of this technology product set

Solution Offering Purpose

A Composite Solution Offering goes across offerings within different offerings groups, especially Core Solution Offerings. Composite Solution Offerings are by nature bridging or cross-cutting. Many of the assets used by the Offering may already exist and as the suite is built out over time, assets can be progressively added to an Offering.

A Composite Solution Offering contains all the elements required to define and deliver a go-to-market offering. It can use a combination of open, shared and private assets.

Instructions
Provide a brief overview of the Solution Offering, including the scope of the offering

Solution Offering Relationship Overview

Mike2 solution groups edm.jpg

Composite Solution Offerings are part of a larger group of offerings within the MIKE2.0 Methodology. Shown at right is the relationship of this offering within the MIKE2.0 Content Model at an Offering Group level.

Instructions
Show where the solution sits in terms of overall Offering Group mapping by highlighting the relevant group in red. This is only to illustrate a high level mapping.

Mapping take place at more detailed level through the tagging of specific MIKE2.0 assets as being relevant to the Solution Offering.

The primary mapping within the suite is to the Solution Capabilities that make up the underlying assets of the MIKE2.0 Methodology.

Mapping at the Composite Solution Offering Level also includes complementary Core Solution Offerings, Business Solution Offerings and Product Solution Offerings.

Solution Offering Definition

Instructions
This section is used to provide a detailed overview of the Solution Offering. It can include:
  • Key themes or guiding principles for how the Solution Offering should be delivered
  • References to success stories
  • Key concepts as part of this Solution Offering

Characteristics Relevant as a Composite Solution

Instructions
This section is used to provide an explanation of those factors within the Offering that make it relevant as a Composite Solution. Involvement or linkage with multiple Core Solutions or other cross-cutting aspects should be noted. This section could include:
  • Enumeration of related Solution Offering groups and what makes the Offering a "composite" one
  • Description of other unique cross-cutting or integrative aspects of the Offering

Relationship to Solution Capabilities

Mapping to Overall Implementation Guide

Instructions
Solution Offerings are mapped to the Overall Implementation Guide in the following fashion:
  • Show the activities required from the Overall Implementation Guide.
  • Provide the overall list of activities required is show through the IM Suite Usage Model
  • The most important activities required from the Overall Implementation Guide are described specifically in relation to the Offering.

Phase 1 - Business Assessment and Strategy Definition Blueprint

Instructions
Most Composite Solutions provide a fair degree of detail for specific activities and accomplishments in accordance with the 5 phases of MIKE2.0. Try to segregate these activities required from the Overall Implementation Guide into the following phases.

Phase 1 tends to emphasize awareness, strategy development, vision, planning and organization.

Phase 2 - Technology Assessment and Selection Blueprint

Phase 2 tends to emphasize functional and non-functional analysis, architecture development, policies, standards, and initial component, application and vendor selection.

Phase 3 - Information Management Roadmap and Foundation Activities

Phase 3 tends to emphasize definitions of business requirements and architecture, plus budgets and schedules. Initial prototypes are generally rolled out in Phase 3.

Phase 4 - Design Increment

Phase 4 tends to emphasize integration and enterprise-wide implications, logical, physical and framework designs, and deployment-grade interfaces and performance.

Phase 5 - Develop, Test & Deploy Increment

Phase 5 tends to emphasize the first meaningful enterprise-scale deployment, with subsequent testing and refinement for later interations or continued scale-up.

Mapping to the SAFE Architecture Framework

Instructions
Solution Offerings are mapped to the SAFE Architecture in the following fashion:
  • Map the Offering to the key architectural components of the SAFE Architecture
  • Also list mapping to solution architecture options, architectural design patterns and logical implementation techniques.

Mapping to the Information Governance Framework

Instructions
Solution Offerings are mapped to the Information Governance Framework in the following fashion:
  • Map the Offering to key Information Governance concepts in the suite.
  • Mappings go across people, process, organization and technology.
  • Also links to Information Management Strategy and how the Offering aligns with the concept of Information Development.

Mapping to Supporting Assets

Instructions
Map the Offering to the Supporting Assets within the MIKE2.0 Methodology. Supporting Assets include:
  • Tools and Technique Papers are methods that can be used to speed the implementation process and includes tools such as Information Maturity QuickScan. These assets focus on specific business or technical problems.
  • Deliverable Templates are framework documents that can be used on any project implementation. Unlike tools and techniques papers, which are focused on process, deliverable templates provide a document structure that defines the output of an activity and its tasks.
  • Capability Statements are overview presentations, selling messages, client cases studies, and vendor case studies related to the IM Solution Offering. They encourage users to take the proposed approach.
  • Software Assets are software artifacts that can be used as part of the Solution Suite. Some software assets are held internally whereas others made available through the open source offering. Assets mapped directly into the open source site are also considered software assets.
  • Engagement Management Assets provide recommended team structures, estimating models and starter project plans for conducting information management projects. Engagement management assets are often internal assets, but some of these assets are available on the open methodology site.
  • Project Examples are example deliverables (both document and software-based) that have been used in information development implementations and can help provide guidance for project implementations. Project examples are typically internally held assets.

Supporting Assets may be open, shared or private assets within the IM Solution Suite. A Solution Offering can map to existing Supporting Asset or proposed new Supporting Assets

Relationships to Other Solution Offerings

Instructions

Show where the Offering fits within the MIKE2.0 Methodology in relation to other Offerings:

  • If the Offering has close relationships or dependencies with other offerings, show these within this section. These can be core, product or business offerings.
  • The Suite Content Model can be used to provide a high-level view

Extending the Open Methodology

By their nature, Composite Solutions cut across boundaries and may represent new thinking or new boundaries. As they are tested and deployed, such Offerings may raise challenges to existing ways of doing business, suggest or require new Offerings, or otherwise raise risks or unknowns.

Relation to Solution Offerings

Instructions
There will be times that Solution Capabilities of MIKE2.0 such as the Overall Implementation Guide, architecture and governance frameworks will contain gaps that will be highlighted by a Solution Offering. In this case it will make sense to add an Extension. Extensions have the following properties:
  • Is of high general value for many different types of projects
  • Is of very high quality
  • Aligns well with the overall approach to Information Development
  • Has gone through an extensive Peer Review process, including a review by the DGMC

The Solution Offering should contain the complete list of gaps and proposed extensions to be added.

Possible Effects on Governance or Policy

Need some more thought here.

Key Unknowns, Uncertainties or Information Gaps

This is a rather open-ended, concluding section that is geared to promote questioning and speculation. Information presented here can help set research and information gathering requirements for the future.

Wiki Contributors
Collapse Expand Close