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.

Business Blueprint Completion

From MIKE2.0 Methodology

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

Contents

Activity: Business Blueprint Completion

Objective. Completing the Business Blueprint brings together all the assets from the previous activities and performs the final strategic analysis to complete the business vision. Whereas the earlier activities have been helping to gather information for the Blueprint, in this activity it begins to come into a more useable form.

Depending on the type of project, the different project release cycles may use different terminology and be broken out in different fashions. Data Warehouses, for example, are broken out along “increments”. Increments are agreed upon combinations of applications and subject areas that will add measurable value to the client.

Within the creation of the Blueprint, the list of projects and a high level plan for the deployment is analysed with the interviewees. The result should be the initial high level plan for the deployment of the agreed upon projects within the larger programme.

Major Deliverables
  • Prioritised Requirements
  • Programme Plan
  • Business Case
  • Programme Blueprint
  • Changes to software environment (if required)
Tasks

Task: Prioritise Requirements and Identify Immediate Work Opportunities

Objective: Based on the Strategic Information Requirements, each information category is evaluated and rated. The result of the ranking will be used to determine the sequence of projects within the larger programme.

This subjective assessment on areas such as Data Quality will be calculated in a more quantitative fashion later on, at which point there may revisions to the overall Blueprint based on the value of the data.

For Data Migration projects, the quality of information will need to be balanced with the business needs for new functionality and available capabilities within an application. Once again, quantitative information analysis may result in revisions to the Blueprint, in the form or either changing priorities or engaging in additional data re-engineering work.

To prioritise requirements, a number of group workshops will be held with interviewees to review results, expand the information and, as a group, prioritise/confirm the sequence of projects in the overall programme


Input:

  • High-Level Information Requirements
  • Information Maturity Assessment
  • Current-State Conceptual Architecture
  • Future-State Conceptual Architecture
  • Recommended High Level Solution Architecture Options


Output:

  • Prioritised High-Level Information Requirements
  • Prioritised Work Opportunities

Task: Define High-Level Programme Plan

Objective: This is a very high level plan showing a sequence of projects and approximate delivery schedule. This will likely include a series of tactical and strategic projects. Tactical projects will be used to get 'quick wins' and meet the most critical information needs of the business. Strategically, the project team will work towards the overall plan defined in the Blueprint. This plan will be revised in Phase 2. It will be taken to the next level of detail in the Phase 3 Roadmap and may also undergo minor revisions at this time.


Input:

  • Prioritised High-Level Information Requirements
  • Prioritised Work Opportunities
  • Recommendations on Current Organisations’ Capability to Deliver Technology


Output:

Task: Develop High-Level Business Case

Objective: At this stage, the initial business case can be formulated for the overall information management programme. Aspects of the Business Case can be done early during the Business Blueprint, but would need to be revised inline with the Technology Blueprint. In the early stages, the Business Case is focused primarily on selling messages and benefits, timelines, options and costs come in the later stages.


Input:

  • Strategic Business Vision
  • Strategic Critical Success Factors
  • Strategic Key Performance Indicators
  • Strategic Success Measures
  • Strategic Change Drivers
  • Prioritised High-Level Information Requirements
  • Prioritised Work Opportunities
  • Recommendations on Current Organisations’ Capability to Deliver Technology


Output:

Task: Assemble Key Messages to Complete Business Blueprint

Objective: This task is focused on compiling the Blueprint into a complete story for the initial, business-focused presentation. Bringing together the working papers and supporting documentation collection from the previous Phase 1 activities, the Blueprint will present a story around each of the above deliverables that were part of the activities.

The Blueprint is complemented by a number of work products – the Blueprint is the summary of this supporting detail. The Blueprint itself will typically need an "Executive Summary" – this would typically be presented in the introductory pages of the overall presentation.


Input:

  • All work products from this phase


Output:

  • Business Assessment and Strategy Definition Blueprint Deliverable Template

Role: Senior Business Analyst

Role: Project Manager

Role: XBR Process Manager

Yellow Flags

  • The team is unable to reach a consensus when prioritising requirements
  • Timelines are very aggressive for implementation and do not allow for contingencies around complex dependencies
Wiki Contributors
Collapse Expand Close

View more contributors