Open Framework, Information Management Strategy & Collaborative Governance | Data & Social Methodology - MIKE2.0 Methodology
Wiki Home
Collapse Expand Close

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.

Infrastructure Dependencies Deliverable Template

From MIKE2.0 Methodology

Jump to: navigation, search
Under review.png
This article is a stub. It is currently undergoing major changes as it is in the very early stages of development and is only a placeholder. Please help improve MIKE2.0 by adding to this article.
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.

The Infrastructure Dependencies task identifies on a service by service basis, the infrastructure needed in order to deliver the proposed functionality. It is common to require that the infrastructure be working, at least in the sense of a beta release, before work begins on an application which assumes that infrastructure. On the other hand, it is often possible to simulate or otherwise stub off some infrastructure capabilities, and develop the actual infrastructure in parallel with project work. The deciding factor here is the degree of risk associated with the infrastructure in question. If the infrastructure project involves significant risks, then those risks should be resolved before application work begins. On the other hand, if project leaders are confident that the infrastructure can be built, then it may be appropriate to begin development of the system before the required infrastructure is in place


I developed this simple chart to talk to our Service Delivery team regarding dependencies based on certain objectives they had set. They were having difficulty understanding the technologies and skills sets they needed to develop within the team to effectively support any objective. In this example we worked on a Standard Desktop deployment using the Altiris suite of tools. You should be able to easily substitute any similar tools such as Microsoft SCCM into the Tool Component section.

Building Blocks - Std Desktop.jpg

Example of Infrastructure Dependencies

Wiki Contributors
Collapse Expand Close