How was Training?

more

“Good overview of EA problems and PEAF as a solution.” - Enterprise Architect, EBRD, UK, Mar 2012

Recommend PEAF?

more

“Yes - Established, well known tool ” - VP Enterprise Architecture, Streamline Health, USA, Jan 2015

Here we see the fundamental structure of the toolkits which are common to adopting a Framework or Ontology for any domain. Toolkits consist of a set of documents defining the processes and products for the domain of interest. The exact content is dependent upon the domain question (Direction, Operation, Transformation or Support) or the sub-domain in question (e.g. Enterprise Architecture or Enterprise Engineering)

The Processes and Products related to Operating the domain in question are defined by that domain. A placeholder process box of Evaluate, Analyse, Modify (as in EMMA) is shown to illustrate that the entire cycle could start again at any time born out of Operation, aka Continuous Improvement.

The Processes related to Implementing the Framework or Ontology in question are defined by that Framework or Ontology but split into two fundamental areas; developing the required changes and rolling those changes out. In addition, a standard process of Mitigate the Risks will always be present.

The Processes related to Preparing to implement the changes and the structure of the Foundation products used are standard.

 

PREPARE

This phase is concerned with setting out the business case for starting an initiative to increase the maturity in a particular domain, and gaining the required remit, budget and resources to do so.  The resulting Implementation Plan is born out of considering the Maturity model, deciding upon the level that an Enterprise currently maps to, the level that it wishes to map to, and the timescales in which it would like to make the transition.

Why Should I Care?

This sets out the basic premise and high level reasons why an increase in maturity in the domain is required.

Select Framework

This selects a framework to help with the domain selected, and performs a high level evaluation of the Enterprises Maturity with respect to it in to determine what work might be required to utilise it.

Understand Framework

Here we do whatever is necessary to understand how to apply the Framework that has been selected. This may entail reading books, attending workshops or training, using a consultancy or any combination thereof depending on the Enterprise and the individuals involved. We also create the Vision document.

Plan Framework Rollout

Here we use the framework to consider our maturity in detail. What level we are at, what level we wish to attain, what the benefits are, and what actions need to be taken in order to effect that increase in maturity.

 

Foundation

The foundation section provides the products required for starting and/or restarting an initiative to increase the maturity in a particular domain

¨      Using these as a starting point allows a rapid definition and proposal to be formulated.

¨      Once formulated, the board can quickly decide whether to pursue the initiative or not.

Maturity

This product details a Maturity Model which describes:

¨      Motivation - The reason we wish to increase our maturity.

¨      Actions - The tasks we need to execute in order to effect an increase in maturity.

¨      Guidance - The things that will guide us as we increase our maturity.

¨      Measures - The metrics that will allow us to know what level of maturity we are at and what would indicate that we have attained an increase in maturity.

¨      Assessment - Our assessment of our level of maturity.

Vision

This product details the overall vision of why an increase in maturity is required and how it will be effected. Without a clear vision that the Enterprise Leadership can understand, agree and believe in, the rest of the initiative will be irrelevant.

Risks

This product details the risks associated with increasing maturity

 

◄◄◄ Previous Page          

          Next Page ►►►
















 

© 2008-2016 Pragmatic EA Ltd