To help others who may be struggling with this topic, I wanted to provide this overview.
To start, I define IT infrastructure by layer:
To make sure you manage all key aspects of each layer, ask yourself the following questions:
Simplifying is always helpful when dealing with complexity and for the keen observer, you might have noticed that if you take the first letter of each aspect I get: ASPEC. Both the layers and ASPECs can be used in many different contexts. For example, when writing a project definition document, you can use these to describe all key and relevant requirements. From an operational management perspective, you can use this to define KPIs. From an organizational perspective, you can use it to find gaps in capability or focus.
To leave you with some examples below is a matrix that illustrates the types of considerations per layer and aspect.
I hope this framework can help you and your teams improve your infrastructure services and assist in driving the right decisions as you implement new Infrastructure paradigms, like cloud computing, during your transformation projects. Don’t hesitate to reach out if you have any questions or comments.
Author:
Edward Wustenhoff 2019
Search Post
Category
Recent Posts
Share Post