MappIT 2.0 – A comprehensive view of your IT Architecture and Governance

Time is ready to make a full recap of the IT Architecture and IT Governance framework and conceptual model underlying MappIT; and then I will show which assessment and analysis scenario it can enable.

The MappIT Enterprise Architecture and Governance framework is split in two areas: Business and IT, where the Business Strategy (what the Company want to achieve) is in the top of the pyramid and is sustained by the Business Operational Model (how this strategy can be achieved through business organization and activities).

In order to run the Business Operational Model 4 IT pillars are required:

  • IT Architecture (systems and infrastructure)
  • IT Initiatives (project in place to implement or evolve systems and infrastructure)
  • IT Spending (staff and budget available to run the IT organization)
  • IT Operational Model (activities performed by IT department and allocation of IT resources to this activities)


For each of the six areas of the framework we have assigned a different colour as describe below:


The framework is then implemented using the following Conceptual model (entities and relationships between them):


This conceptual model enables many different scenarios; in the following table I will recap this scenarios and their link to more detailed tutorial, which explain in more details them.

IT Application Architecture Assessment
This scenario is typically the first step in an IT Governance or IT Architecture project, and is related to the discovery of the application architecture elements (including systems, modules, services, interface and data entities) and their relationships (which interfaces connect which applications, which entities are mastered in each module…) You can get a detailed description of this scenario here.
IT Infrastructure Architecture Assessment
This scenario is an optional one that you can use in project where an Infrastructure Assessment and mapping is required. This is typically useful for example in projects like Server Consolidation, Virtualization, Outsourcing and Data Center moving. In addition to map the application landscape, you may need here to map also the infrastructure devices (servers, network equipment, clients, telephone, tablets…) and their relationship with the applications (which server host which application) You can get a detailed description of this scenario here.
Business Context Analysis
This scenario is the starting point for discovering the Enterprise Business Architecture; it include collecting information about the Business Macro Context (for example refer to the PEST framework: Political, Environment, Social and Technological topics), the Market context (for example refer to the Porter Framework which include information about Suppliers, Customers, Competitors, New Entrants, …) and Company Context (Financial, Skills, Assets,…). It allow also to collect specific information about the Business Model which include Products portfolio, Customer segment, Channels. You can get a detailed description of this scenario here.
Business Operational Model Discovery
This scenario is the first bridge between Business and IT Architecture.. It allow to discovery the Operational model of the company in terms of its internal Organization and the in terms of Business Processes and Activities. These Processes and Activities can later be linked to the Module mapped in the Application assessment, in order to understand which application support which business processes You can get a detailed description of this scenario here.
Business Alignment Analysis
This scenario is the key Analysis used to identify which are the Business needs (in terms of Business Drivers, Objectives) starting from the Business Context and translating these needs into enabling Capabilities (the functionalities and detailed Requirement) that must be implemented and supported by IT systems; this is typically a TO BE Analysis. Considering the complexity of the business scenario, typically each Objective is related with a many to many relationship both with Drivers and Capabilities. This is called Alignment analysis because try to align the Business with the IT. You can get a detailed description of this scenario here.
Impact Analysis
This scenario is a typical analysis used to foresee which will be the impacts of implementing a subset of requirements belonging to a Capability identified during the Alignment analysis. The impact identified can be technical impacts (new, updated, decommissioned interface or module) and business ones (e.g. organization, skills and processes changes). Each impact is also linked to the specific asset impacted (module, interface, organization, process….) and an estimation of budget required to manage the impact is required. Finally the capabilities 8and so related impacts) are grouped together into implementation projects defining a roadmap for delivering the required business needs. You can get a detailed description of this scenario here.
Organization Assessment
This scenario is an IT Governance assessment aiming at identifying how the IT department is organized in terms of Organization Unit, Staff and related Skills. These skills can be collected through self-assessment from the IT people. You can get a detailed description of this scenario here.
IT Spending and Sourcing Review
This scenario is another IT Governance assessment aiming at identifying how the IT organization operate (which are the typical Activities that are performed) what are the resources available to perform these activities (external Budget and internal Staff) and how much of these resources are allocated to the activities. This review can highlight the mix and level both of sourcing and spending in each area of the IT organization and related to different modules and on-going projects. You can get a detailed description of this scenario here.
Shaping the IT Organization
This scenario is the design of the target Organizational and Operative model for an IT Department based on the current an expected level of resource available in the future (external budget and internal staff). This design try to allocate the available resources in the optimal way applying a reference operative model to the target activities based on the level of control, skills required and maturity of the application/project to be managed by the department. At the end of this analysis you will know the target sourcing and spending allocation and the impacts (the delta in terms of IT Staff and Budget required to implement the target scenario). You can get a detailed description of this scenario here
Skill Gap Analysis
This scenario is conceptually the last task of our long journey. Once you have shaped the new IT organization you need to evaluate also the impact of moving people to a different set of activity. This means that you have to define the roles and skills required to perform a specific activity and the evaluate the gap between the expected skills and the real skill that people have. This analysis can highlight areas of gaps to be covered through formal training and on-the-job activities, that in term of impact must also included in your analysis. You can get a detailed description of this scenario here.

 

Advertisements

About FrankITecture

I'm an IT Consultant with many years of experiences in IT Architecture, IT Governance and IT Strategy projects in many Market Sectors (Telco, Finance, Retail...)
This entry was posted in Uncategorized and tagged , , , , . Bookmark the permalink.

Please, leave a comment or suggestion

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s