From MIKE2 Methodology
Activity: Technology Blueprint Completion
Objective
In the Technology Blueprint Completion activity, the final steps are conducted as part of the overall technology strategy and the overall set of deliverables are brought together. The completed deliverable then describes the steps necessary to upgrade the current infrastructure to the future environment, often over a multi-year programme.
Particular attention should be given to describing the intermediate states in implementing the blueprint. The intermediate points are stable states of the system in which some part of the final functionality has been implemented. The more clearly the intermediate states can be described, and the more useful and functional each of them is in its own right, the more likely it is that the whole project will be successful.
Major Deliverables
The overall Blueprint is completed by summarising work products of prior activities. Within this activity, a number of final tasks are completed that produce detailed work products:
- Technology Risks & Constraints
- Implementation & Deployment Plan
- Business Case (Revised from initial version)
Tasks
Revise Blueprint Architecture Models
Objective:
The purpose of this task is to make any revisions to the overall Blueprint architecture before proceeding to the first increment. Based upon results of the previous task, the team should make adjustments to the architecture before proceeding to the first iteration.
The overall Blueprint Architecture consists of the Current-State and Future-State Strategic Conceptual, Logical and Physical Architecture. It also includes High Level Solution Architecture options.
Input:
- Overall Blueprint Architecture
- Deployed Development Environment
Output:
Define Major Technology Risks and Constraints
Objective:
This task supplements the Gap Analysis and focuses on the risks associated with the gaps identified. The identification of the risks associated with the proposed information management environment highlights the exposure to the client in not addressing the gaps. This allows the client to make an informed decision on what risks the organisation will be exposed to by deferring or not implementing and or all of the recommendations put forward in the Business and Technology Blueprint. Hence, the deliverables from this task take on two characteristics, a technical evaluation as well as a business risk. The risks must therefore be stated in business terms.
Major Technology Risks and Constraints for the Strategic Architecture should incorporate:
- Technical Risk
- Probability of occurring
- Impact to the project/organisation
- Probable cost
- Risk mitigation
Input:
Output:
Define Business and Technology Capability Deployment Timeline
Objective:
The purpose of this task is to develop the overall plan to deploy the new technologies within the framework of the existing infrastructure. Any ability to leverage or reuse any existing hardware, software, infrastructure and interfaces should be identified at this stage and representative timeframes indicated.
Input:
- Prioritised Requirements
- Immediate Work Opportunities
- High Level Programme Plan
- High Level Business Case
- Overall Blueprint Architecture
Output:
Revise Business Case
Objective:
The Business Case itself should be revisited at this point. In phase 1, the Business Case was described in terms of expected benefits, risks, assumptions, and projected costs. It is now possible to describe each of these in greater detail, and to add information about schedule, including interim milestones. Based on the new architectural components, technology costs can be accounted for and more accurate predictions can be made about the skills required for implementation.
Input:
- Prioritised Requirements
- Immediate Work Opportunities
- Initial Business Case
- Tools and Technologies Selected
- Proposed Iterations of Deployment of New Functionality
Output:
Define Roadmap Mission Statements
Objective:
The deliverable from this task is a text statement describing each of the planned increments. A particular focus is given on the initial project as this task is repeated in Phase 3. It should be written in the context of the overall Business Case and provide a lead-in to the next phase of work.
Input:
- Business Case
- Vendor Selection
- Proposed Iterations of Deployment of New Functionality
Output:
Assemble Key Messages to Complete Technology Blueprint
Objective:
The purpose of this task is to bring together the overall message for the Business and Technology Blueprint. The Technology Blueprint provides a summarised version of all detailed working papers for the phase, which include:
- Strategic Functional Requirements
- Strategic Non Functional Requirements
- Gap analysis of Current State vs. Strategic Requirements
- Future State Logical Architecture
- Physical Vendor Options against Logical Architecture (multiple physical architectures)
- RFP issued, technology vendors selected
- SDLC Preparation : Development Environment, Hardware and Software Procurement, SDLC Procedures, Testing Strategy in place
- Technology Risks, Constraints, and Deployment Timeline of Information Management Capabilities
Input:
- All work products from Technology Blueprint phase
Output:
Core Supporting Assets
Yellow Flags
- Major risks highlighted around technology timelines without corresponding contingency plans
- Revisions to Business Case and Capability Timeline show only long-term business benefits
- Revisions to Business Case and Capability Timeline show only technology benefits
Key Resource Requirements
BlogMarks
del.icio.us
digg
Furl
Simpy
smarking
