Reference Books

Focus Books

Study Guides


BOOK - Enterprise Transformation - A Pragmatic Approach Using POET


◄◄◄ Previous Page         


          Next Page ►►►

Here we show how other frameworks map on to the Transformation cascade (From strategy to Deployment) that POET defines.

The Enterprise Context consists of all the things that are not part of The Enterprise (i.e. not directly under its control) but affect or is affected in some way by it. Things like Customers, Suppliers, Partners, Regulators, etc.

The thick black line across the diagram marks the delineation between Project Portfolio Planning above and Project Execution below.

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 actually physical things. All models are shown to exist in two fundamental states, Current and Target. There are also, of course, intermediate states but they are not shown to aid readability.

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.


Zachman 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.


PEAF is an Enterprise Architecture Framework for two reasons:

¨      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.


TOGAF is mostly a Project IT Architecture (PITA) framework for two reasons:

¨      Vertically although it includes some Roadmapping it is mainly concerned with projects.

¨      Horizontally the blue box is shown to not cover the entire width of the Enterprise because TOGAF’s domain is really only IT. It does cover things that are not IT, such as processes and business things, but only where these business things have some relationship or connection to IT. Consequently, there are other things in the Enterprise, that do not use IT, that TOGAF ignores.


ITIL in its original form 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 Services.


COBIT covers four main domains:

¨      Evaluate Direct, Monitor (EDM) and Align, Plan Organise (APO) map to the Management domain of the Roadmapping level of POET.

¨      Build, Acquire, Implement (BAI) maps to the Management domain of the Roadmapping Initiating, Elaborating, Constructing and Transitioning levels of POET.

¨      Monitor, Evaluate, Assess (MEA) maps to the Governance domain/interface between the Roadmapping Initiating, Elaborating, Constructing Transitioning and Using levels of POET.

¨      Deliver Service & Support (DSO) maps to the Using domain of the Operation/Support domains of DOTS.


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 projects.

¨      Horizontally - it covers the entire enterprise including but NOT LIMITED to IT.


◄◄◄ Previous Page          

          Next Page ►►►

Questions to ponder...

How do you think TOGAF, PEAF, PEEF, COBIT, ITIL and POET relate to each other?

Which Frameworks do you use?

Which overall framework for Transformation do you use to map other to?

© 2008-2018 Pragmatic EA Ltd