MIKE2:Product Roadmap

From MIKE2.0 Methodology

This article is a key aspect of the Open Methodology Framework and has therefore been protected. Propose changes to this article on its corresponding discussion page.

The Product Roadmap for the MIKE2.0 Methodology provides a list of planned functionality to be incorporated into the MIKE2.0 Methodology against a future timeline. In particular, it focuses on the content to be added to the Core MIKE2.0 Methodology in each Release Cycle.

Guiding Priorities of every Roadmap

• Addressing Known Issues
• Incorporating Recommended Extensions and new Core Supporting Assets
• Meeting suggested functionality from Talk Pages and Suggested Future Requirements

Planned Functionality for Next Release

During the beta period, content will be changing from the Core MIKE2.0 Methodology independent from a Release Cycle. Therefore, there will not be a formal release of content that is part of the Core MIKE2.0 Methodology at a set time period as there will be in future releases.

Long Term Release Roadmap

We have been at MIKE2.0 for a while, but there is a still lot of work to do. Some of the major activities include:

• Keep building the community!

• Launch a Consortium to act as stewards of the open approach. Our planned approach is described here.

• Get better coverage across Information Management in areas such as Business Intelligence/Enterprise Performance Management, Data Center Management and unstructured content

• Work of making MIKE2.0 a more useable plan with additional detailed deliverable templates

• Keep building depth around solutions and supporting assets

• Help drive new theories in Information Management to solve the complexity

• Drive the product specific story with vendors to enhance the standard

• Drive a stronger business-IM story through Business Solution Offerings

• Release new capabilities to the open methodology framework to enhance collaboration

• Put a greater focus on internationalization through multi-language sites

Our long-term goal is to provide a better to link the approach to executable code through an Organizing Framework for Information Development