In the last tutorial we show how to map the Business Strategy in terms of Context, Drivers, Objectives. We showed how to define the Functional Architecture in terms of Enabling Capabilities and related Requirements and how to link the Functional Architecture to the Business Strategy.
Now we want to show:
- How to link the Functional Architecture to the Technical architecture
- How to map Impacts of implementing new Capabilities or enhancing existing ones
- How to aggregate this impacts in Activities/Phases/Projects in order to manage these impacts and implement the Capabilities
First the first point we can go through the IT Module Screen and select the “Capabilities coverage map” tab. From this tab we can see a matrix of Capabilities vs Systems and we can map the Level of support of each module related to each capability (meaning what percentage of the functionalities available through the capabilities are or can be delivered through the selected Module).
Using this simple task you have correlated the Functional and System architecture and so the Business Strategy and the System Architecture.
Using MappIT tool you can the later create a Visio map, which display the network of correlation between them.
For the second item we have to perform an Impact Analysis, which means going through all requirements related to each capability and identify the impacts (in terms of Business, Process, Organization, IT) that are required in order to implement a set of requirements onto a Capability. For example, in order to have the “create/delete/update Order item” for the Order Management capability in the Order Management System we have to adapt the GUI screens and create a new Interface between the Order Management Systems and the Provisioning system.
So we have to:
- Create 2 impacts (1 for GUI and 1 for system interface)
- Group the requirement “create Order item”, “delete Order Item” and “update Order Item” together
- Link the 2 impacts to the related requirements
- Link the 2 impacts to the affected items (the Interface and the Order Management System)
- Collect some additional information about this impacts (e.g. complexity estimation)
For doing all of these tasks we have to go through the Business Impact form:
Through this form we create the impacts and also perform all other described tasks:
For the last step we need first of all to create the Initiative through the proper form.
Then we need to group together a set of capabilities (and related impacts) into an Initiative; this can be done through the Business Capability form, where we can set which Initiative will address this Capability.
When this is done we can go back to the Initiative form as see all Capabilities linked to the Initiative, but also all of their impacts as well.
On the other side, we also know what is the Business Priority of each capability and so what is the business priority of the overall initiatives.
We can than put together both Capability and Initiative priorities and Capability and Initiative impacts in order to define a proper implementation roadmap.
For example we can display project complexity vs priority in order to determine the project roadmap, starting first project with high priority and low complexity.
You can also drill down to the capability level:
But more interesting you can link Initiative and Capabilities togheter like in this chart, where we show initiatives Complexity vs. Priority, broken down by capability complexity.
After project has been planned and approved they will start, so:
- project activities will start
- risk and issues will arise
- IT department will start to spend money and allocate internal staff on this activities
All this information can be tracked using MappIT; for example we can add information related to project risk and issues….
.. as well as the project phases and key decisions…
We can also see the Budget and Internal IT staff allocated to this Initiative; this will be shown in a future tutorial.
In this way we can track the full project portfolio lifecycle and monitor also the progress (phases, % of completions,…) and issues/risk related to it.