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.

Strategic Mobilisation

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
Content Model Relationship

Contents

Activity: Strategic Mobilisation

Objective

In the Strategic Mobilisation activity, the team is introduced to the organisation and begins setting the initial direction for the project. Afterwards, team members begin to establish sample deliverables, ultimately modifying them to reflect some of the key systems and processes. This helps the organisation more easily understand the approach by conveying important concepts in a familiar language.

Major Deliverables

Tasks

Conduct Initial Direction Setting with Sponsor

Objective:

This is the initial meeting with the programme sponsor. Ideally, this meeting takes place in person, as it enhances familiarity. Ideally, the sponsor should meet the teambefore the formal meeting. This meeting should serve to

  • arrive at an understanding of the priorities of the project
  • understand the project's key stakeholders
  • begin to establish insight on the programme’s current activities
  • work towards creating a long-term vision

Input:

  • RFP and RFP Response
  • Signed Engagement Letter

Output:

Meet with Key Stakeholders

Objective:

After initial meeting with the project sponsor, this second meeting serves to introduce key players on the project to one another. Once again, this meeting should take place--if possible--before a group workshop session begins. And the meeting should content similar to what was covered in the the meeting with the overall programme sponsor.

The meeting should focus on obtaining preliminary insight into the project's current activities and future vision. The stakeholders need to understand that this is the first in a series of meetings. What's more, not all topics will be covered in the initial meeting.

Input:


Output:

Begin Collection of Artifacts

Objective:

In this task, the team begins to collect artifacts including: 

  • existing architecture models
  • design documentation
  • standards
  • guidelines
  • requirements

This is an ongoing task and drives subsequent tasks throughout the implementation of the programme. It is imperative to start this process early, as it save time in the future.

Input:


Output:

Understand Current State of Project Activity

Objective:

This task reviews existing project documentation and the project's current status. In this stage, the parties continue to build an understanding of the projet's current state. This is imperative now that the team is on the ground. The team should use MIKE2.0 Supporting Assets as a guide, Team members should make any necessary modifications to these templates early in the projecess. Modifications typically mean adapting templates to use the organisation's language in relation to systems, processes, and deliverables.

Input:


Output:

Establish Charter for Information Management Programme

Objective:

In this stage, the objective is to establish the contractual scope of work for the programme. This will often be an addendum to the original contract that has been defined and typically takes place after the team begins work in earnest. Key areas covered in the Charter include:

  • Scope and Approach
  • Team Structure and Roles and Responsibilities
  • Timelines, Milestones and Deliverables
  • Dependencies, Assumptions and Risks

A summary of the Charter for the strategy phase is rolled up into the overall Blueprint.

Input:


Output:

Introduce Overall MIKE2.0 Programme Plan

Objective:

The objective here is to introduce the overall MIKE2.0 approach for conducting the project. It is here that timelines for the project are developed and refined. This information will typically be given during the RFP response; it may be modified during the mobilisation activity as the team gains a better understanding of client expectations

Input:


Output:

Core Supporting Assets

Yellow Flags

  • Lack of a signed contract
  • Major scope conflicts during interviews

Key Resource Requirements

Wiki Contributors
Collapse Expand Close