How was Training?


The PEAF course experience leaves me wanting to get started, and implement what I learned. I am not confused as to where to start. - EA consultant, Elyon Strategies, USA, Jan 2015

Recommend PEAF?


Yes - Just because it is another framework to take ideas from. - Software developer, Hexaid, Argentina, Jan 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  




<< Previous <<

>> Next >>

PEAF inherits and utilises the Methods, Artefacts, Culture and Environment defined in POET.

Who Should Read PEAF?

Anyone and everyone that is involved (in whole or in part) in the Strategising and Roadmapping phases of Enterprise Transformation (e.g. CxO's, Executive Management, Enterprise Architects, Strategic Transformation Planners, members of the PMO, etc.) and with the Governance and Lobbying of project execution (e.g. Project Managers, Business Analysts, Enterprise IT Architects, Solution Architects, Technical Architects, etc).

The book is intended for Enterprise Architects, Business Architects, IT Architects, process-designers and others who deal with the practical implications of whole-of-enterprise issues.

It should also be useful for Strategists and Service-managers, and for anyone else who works with other enterprise-wide themes such as supply-chains, value-webs, quality, security, knowledge-sharing, sustainability, business ethics and social responsibility, or health, safety and environment.

What Does PEAF Tell Me?


To read, understand and adopt PEAF you must have first read and understood POET.

PEAF does not tell you how to be a CxO, Executive, Strategic Planner, Enterprise Architect, Business Architect, Solution Architect, Portfolio Planner, Portfolio Manager, etc, etc, etc.

What PEAF does do is expose a holistic environment and context of Methods, Artefacts, Culture and Environment that all of those people exist within. The glue that brings all the parts together into a choreographed whole which makes the whole so much more than just the summation of its parts.

PEAF asserts that people working within the Strategising and Roadmapping phases of Transformation already know how to do what they do. The problem is not them. The problem is the context (Methods, Artefacts, Cultural and Environmental things) that they are forced to work within. PEAF aims to increase the maturity (effectiveness and efficiency) of that context, enabling people to achieve their full potential. Increasing the maturity of the context they work within, to one that supports, enables and makes their work easier rather than one which hinders, impedes and makes their work more difficult.

PEAF places its emphasis on the one practical issue that causes the most problems for EA efforts: how to get started and keep going, delivering real and verifiable results within the constraints and complex, challenging realities of any large Enterprise. In a sense, PEAF was born out of failure - out of identifying all the myriad of ways in which EA efforts fail in real business practice, and then devising ways to prevent these sources of failure from occurring.


2008-2016 Pragmatic EA Ltd