MIKE2:Protected Content

From MIKE2 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.

Protected Content are those articles that can only changed by members of the Data Governance and Management Consortium. Examples of Protected Content include:

• Most aspects of the MIKE2.0 Framework such as the Contribution Process
• All Activities from the Overall Implementation Guide, such as Organisational QuickScan for Information Development
• Key concepts such as Information Development
• MIKE2.0 Solutions and MIKE2:Supporting Assets that are part of the Core MIKE2.0 Methodology such as the SAFE Architecture and Information Maturity QuickScan

The rationale for making some MIKE2.0 content protected is that as MIKE2.0 is a methodology, stability is required across core content so that users can implement solutions using a reliable approach. Changes to the core content occur through planned Release Cycles and against a defined Product Roadmap.

Whereas a fairly high percentage of the content that was put forward as part of the Baseline Release was protected, this will not be the case for the majority of new content that is added in the future. All new content will go through the Contribution Process defined as part of MIKE2.0 and some assets will never be protected. Contributors will always be able to offer feedback on an article on its Talk Pages.

It is also possible that the currently implemented approach of protecting content will be made more flexible in the future; discovery of the most effective model for content protection is one of the activities of the initial Beta phase of MIKE2.0.