When you decide, or are involved, in an evolution project regarding your Organization division, perhaps your Company is willing to transform it in an Enterprise Architecture Capability, in other words a set of resources dedicated to design and support change management using comprehensive frameworks, like TOGAF.
It’s a good moment to think carefully about your objectives, and you can use TOGAF itself as a supporting framework for this project (TOGAF manual describes this task in the “preliminary” phase).
The core of this activity will be synthesized by:
- you “as-is” practice, that is your baseline Architecture Capability;
- the desired target Architecture Capability.
The differences between those two situations will be described using a list of gaps, that will be the starting point for your project definition.
Using Archimate – the modeling language that integrates very well TOGAF in many parts – we can describe these elements.
The figure is only an overview, but the gaps highlighted will guide you through a series of questions that will define your evolution:
- people and skills involved,
- organizational position of the Architecture team,
- usage of internal/external resources,
- scope (horizontal and vertical) of the analysis,
- interaction with IT, HR, Board, etc.,
- tools, standards,
- project management practice,
and so on.
This will be also a good opportunity to start practicing, in your “real” business, your new organizational structure. At the same time, during this project, you will produce – as a deliverable – an initial Enterprise Architecture, covering the basics layer of Business, Data, Application and Technology. This initial Architecture, stored in your Architecture Repository, will be used and refined in your following architectural projects.