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.

Major Technology Risks and Constraints for Strategic Architecture Deliverable Template

From MIKE2.0 Methodology

Share/Save/Bookmark
Jump to: navigation, search
This deliverable template is used to describe a sample of the MIKE2.0 Methodology (typically at a task level). More templates are now being added to MIKE2.0 as this has been a frequently requested aspect of the methodology. Contributors are strongly encouraged to assist in this effort.
Deliverable templates are illustrative as opposed to fully representative. Please help add examples to this template that are representative of the proposed output.

Overview

The Major Technology Risks and Constraints for Strategic Architecture 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.

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

Example for Technology Risks and Constraints for a Strategic Architecture

Listed below is an example of Technology Risks and Constraints for Strategic Architecture:

Technology Risk Assessment

Risk Likelihood Impact Mitigation
There is a risk of project delay and cost overrun due to the Technical Solution Operational Complexity: the system has demanding capacity and performance objectives. The solution will require high-level of performance engineering, testing and tuning.
.
Medium Medium Provide time in plan to allow for performance evaluation (bench marking or piloting) of target architecture.
Ensure staffing has appropriate performance engineering expertise.
Ensure adequate Performance / Capacity Testing services support is planned.
Consider technology vendor or 3rd party benchmarking services.
There is a risk of high (actual) cost variance due to potential lack of detail provided to develop a cost schedule for technical components. This may result in costs derived with limited requirements or technical definition.
High Medium Ensure that there is sufficient sizing and capacity analysis to confirm infrastructure costs.
Require quantitative analysis or use commercially available sizing tools to justify pricing.
Add piloting or bench marking activity with subsequent repricing milestone if sufficient information will not be available during Evaluate phase.
There is a technology acceptance risk due to the impact of Technologies: the solution has major impact on current business processes and introduces technologies unfamiliar to users.
Low Medium Ensure that adequate impact analysis is conducted.
Ensure plans for additional promotion and communication of the project initiatives and status to facilitate user acceptance.
Consider planning organisational change assessment activities.

There is a risk of delay to delivery, unplanned effort to resolve performance, security and management issues, and require significant rework as Service Oriented Architecture is a new approach for the Company.
Medium Medium The knowledge and best practices of third party systems integrator will be leveraged.
Invited technology vendor lead architects to assess the solution viability and optimisation. No major issues have been identified.
There is a risk of additional development, time and cost to improve system performance if the overall run time system performance cannot meet business objectives and measurements
Medium Medium Leverage the Test Lab to identify potential system bottlenecks.
Identify performance criteria for early performance testing engagement.
Conduct performance testing early in the Analysis & Design Phase and again at Build Phase.
Ensure an early prototype to test the integration of components.

Wiki Contributors
Collapse Expand Close