The Open Source Standard for Information Management

Personal tools
Refresh Collapse Expand Close
  • 38.107.191.116
  • Talk for this IP
Members
Refresh Collapse Expand Close

To join, please contact us.

Improve MIKE2.0
Refresh 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.
Add Portlet Add Portlet

MIKE2:Content Relationships

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
The MIKE2.0 Methodology Activity Model

The Overall Implementation Guide provides the governing set of Phases, Activities, and Tasks for the MIKE2.0 Methodology:

  • Phases - The major lifecycles of a programme. The MIKE2.0 Methodology has 5 phases as part of its continuous implementation approach.
  • Activities - Describe major units of work through a focus on key concepts and deliverables.
  • Tasks - Describe the detailed set of steps within an Activity that are required to produce the overall set of deliverables.


For each Phase, Activity and Task, the following are defined:

  • Objective - an overview of the particular step
  • Input - dependencies to initiating the particular step in the process
  • Deliverables/Output - describe what is completed out of this step in the process


At the Activity level, the following are also defined:

  • Core Supporting Assets - references to Key Supporting Assets. Only Public Supporting Assets are listed within the Overall Implementation Guide. A number of other Supporting Assets are linked into the methodology through either internal knowledge management systems (internal version) or through categories in the open methodology.
  • Yellow Flags - issues to watch out for that typically cause problems
  • Key Resources - typical types of resources that are needed to perform an activity. This is a very high-level model; MIKE2.0 estimating tools should be used for more accurately assessing this area.

Each of these areas will are built over time to supplement the core methodology. Contributors to MIKE2.0 can recommend extensions and new Core Supporting Assets to the Overall Implementation Guide.

Add a portlet to your desktop
Close