Here we show how other frameworks map on to the
Transformation cascade (From strategy to Deployment) that POET defines.
The ellipses of POET show the phases of transformation while
the rounded boxes show the models used. The boxes with square black lines are
not models but actual physical things. In between each phase of transformation,
we show the Governance and Lobbying disciplines of POET (using Transformation
Debt™) which, as you will see later, is the key to making the whole coherent,
connected and aligned.
The structure of the Enterprise is represented by the
Methods, Artefacts, Culture and Environment of the Enterprise. Each of these is
split into two categories. Things that are connected to (use) the IT of the
Enterprise and things that are not. So, for example, there are Methods
(Processes, etc) that are connected to (use) IT, but there are other processes
in the Enterprise that are not connected to (use) IT. This is also true for The
Artefacts and Culture columns. The Environment column represents different
technologies that the Enterprise uses and is split into one column for
Information Technology, and one column for all other technologies (Mechanical,
Electrical, Biological, Chemical, etc)
These categories will be used to overlap various frameworks
on, so we can see where each fits and where the overlaps or gaps are.
The thick black line across the diagram marks the
delineation between Project Portfolio Planning above and Project Execution
Zachman is an Enterprise Structure Framework, which maps
almost one-to-one to POET’s structural and transformational levels although we
also show the missing Perspective and Model.
It should also be noted that this mapping is only general as
there are other anomalies such as Zachman’s Architect and Engineer perspectives
(shown in Yellow and Green) which are actually fundamental perspectives which
occur at all levels not just at one.
TOGAF is mostly a Project IT Architecture (PITA) framework,
for two reasons:
Vertically although it includes
some Roadmapping it is mainly concerned with projects, but only goes down to
the Elaboration level, playing only a governance role to Construction and
Horizontally the blue boxes show
that it only covers IT things in the Environment column and does not cover any
other technologies. It only covers the Methods connected to IT, the Artefacts
connected to IT and does not cover Culture at all.
COBIT is an IT Governance & Management Framework, and covers
Roadmapping and all project phases, plus the Operations domain (of IT
ITIL is a Service Management Framework. In its original form, it
only covered the Service Operation or Management area, but over recent years
has grown up the transformation stack although its domain is still only really IT
IT4IT is a reference model for the IT used by the IT department
of an Enterprise. Its width is narrow because it shows that it does not cover
the IT for the entire Enterprise, but only the IT used for the IT department of
the Enterprise. It does, however, extend up into the Roadmapping and Strategy
phases, and down into the support area also.
DevOps is a software development framework. It is a mindset, a
culture, and a set of technical practices that combines software development
(Dev) and information technology operations (Ops) to shorten the systems
development life cycle while delivering features, fixes, and updates frequently
.in close alignment with business objectives.
PEAF is an Enterprise Architecture Framework, for two
Vertically - it covers the Strategising and Roadmapping
phases and is therefore concerned more with strategic cross-project things
rather than tactical project‑specific things. It is concerned with
projects a little, but only from the EA Governance perspective - down to
projects and Lobbying up from Projects - This is where the concept of Transformation
Debt™ comes in that you will see later.
Horizontally - it covers the
entire enterprise including but NOT LIMITED to IT. It covers the Methods,
Artefacts, Culture and (technology) Environment of the entire Enteprise.
PEEF is an Enterprise Engineering Framework, for two reasons:
Vertically - it covers the Initiating to Transitioning phases
and is therefore concerned more with tactical project-specific things rather
than strategic cross-project things. It is concerned with the entirety of
Horizontally - it covers the
entire enterprise including but NOT LIMITED to IT.