From MIKE2 Methodology
Activity: Strategic Mobilisation
Objective
In the Strategic Mobilisation activity the team is introduced to the organisation and begins the initial direction setting for the project. They also begin to take the sample deliverables and modify to reflect some of the key systems and processes. This helps the organisation more easily understand the approach by conveying concepts in a familiar language.
Major Deliverables
- Interview Notes
- Initial revisions to template deliverables
Tasks
Conduct Initial Direction Setting with Sponsor
Objective:
This is the initial meeting with the programme sponsor, it is best to have this face-to-face to build familiarity and ideally the sponsor should be met before the formal meeting. It should be used to understand the priorities of the project and its key stakeholders and begin to establish insight on the programme’s current activities as well as its long-term vision.
Input:
- RFP and RFP Response
- Signed Engagement Letter
Output:
Meet with Key Stakeholders
Objective:
Following on from the initial meeting with the project sponsor, this meeting is to gain familiarity with the key players on the project. Once again, it is good to meet people if possible before a group workshop session begins. The content of the meeting should be similar to that with the overall programme sponsor, mostly focused on gaining preliminary insight into current activities and future vision. The stakeholders should be made aware that these are the first in a series of meetings and that not all topics will be covered in the initial meeting.
Input:
Output:
Begin Collection of Artifacts
Objective:
In this task, the team begins to collects artifacts such as existing architecture models, design documentation, standards, guidelines and requirements. This is a long-running task in that it is plays a part in many tasks throughout implementation of the programme. The idea behind starting this process early is that it will save time in the future.
Input:
Output:
Understand Current State of Project Activity
Objective:
This task reviews much of the existing project documentation and status. The idea at this stage is to continue to build an understanding of where things are at on the project, now that the team is on the ground. The team should use MIKE2.0 Supporting Assets as a guide; modifications to these templates should be made early to use the organisation's language in relation to systems, processes and deliverables.
Input:
Output:
Establish Charter for Information Management Programme
Objective:
Establish the contractual scope of work for the programme. This will often be an addendum to the original contract that has been defined, once the team gets on the ground. 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:
Introduce the overall MIKE2.0 approach for conducting the project with representative timelines for the strategy project. This information will typically be given during the RFP response and 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
BlogMarks
del.icio.us
digg
Furl
Simpy
smarking
