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.

Continuous Implementation Phases

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
The Continuous Implementation Phases of MIKE2.0

The Continuous Implementation Phases of MIKE2.0 are those phases that repeat for each implementable increment. As part of the Extreme Blueprinting and Roadmapping approach, the strategy for MIKE2.0 is done to set the initial vision and the Continuous Implementation Phases are repeated a number of times throughout the life of the programme.

The Continuous Implementation Phases are:

This approach divides the development and rollout of the entire system into a series of implementation cycles, which identify and prioritize the portions of the system that can be constructed and rolled out before the entire system is complete. Each cycle also includes a feedback step to evaluate and prioritize the implementation results, strategy changes and improvement requests on the future implementation cycles.

= Rationale

This Continuous Implementation concept is central to the information management implementation approach. This concept provides an opportunity to divide the project team into groups organized by implementation activity, specializing on a specific implementation role. As the implementation process iterates through the implementation cycles, the processes and skills of each implementation activity team are refined, enabling the activity team to improve quality and reduce cycle time. Implementation activities also provide a mechanism for establishing a continuous system enhancement and feedback process for the client when the initial implementation team is no longer involved in the project. forfait b and you rio bouygues portabilité du numéro calcul IMC rio orange

Comparison

This approach is different than the traditional traditional linear or waterfall approach to systems development. The key benefits include:

  • Work is broken into manageable pieces, delivered in short cycles
  • Alignment across different projects into a single programme
  • A focus on re-factoring to improve what already exists
  • An initial focus on the Foundation Activities that are high risk for Information Management projects

Continuous Implementation includes a set of Continuous Improvement Activities

Wiki Contributors
Collapse Expand Close