How was Training?


Very positive. The instructor was very knowledgeable and passtionate about the subject. - Technology Architect, Freshfields, UK, May 2013

Recommend PEAF?


Yes - Easy to understand - straightforward. - Solutions Architect, Boral, Australia, Feb 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  




<< Previous <<

>> Next >>

The artefacts used in our Enterprise for Transformation are of insufficient maturity to be able to cope with the work required due to rising complexity and volatility.

The problem is not one of a lack of volume. In fact volume - too much information - is one of the problems, but there are many others. Artefacts (Structural and Transformational) are:

      Scattered all over the Enterprise

      In all departments and not just the IT department.


      The same information exists in multiple places

      Out of date

      Information that was created has not been kept up to date.

      Owned by multiple people

      Multiple people are likely to think that that have the "master list" of something.

      No clear ownership

      There are no clearly Identified individuals who are deemed responsible and accountable for various pieces of information.

      Utilise different languages

      One list of "Services" may describe something completely different to someone else's list of "Services"

      Stored in unstructured formats



      Exist in many and varied locations:

      In people's heads


      On the intranet

      On whiteboards

      Pasted to walls

      Stored in many different formats:

      Excel spreadsheets

      Word documents

      PowerPoint slides

      Visio diagrams

      Web Pages

      Access databases

      Corporate databases

Against this backdrop it is surprising that anyone manages to do any work at all! But people do. People are very adaptable (unfortunately!) especially when it comes to a lack of information. This is because information doesn't follow the laws of physics. For example, in the physical world it is not possible to bake a cake before turning on the oven, but with information it is quite possible to create one artefact that depends on another even though the artefact it depends on does not exist! In the physical world it is not possible to put the roof on a house before the walls have been erected, but with information it is quite possible to run projects and build things without a proper strategy or roadmap.

We are not saying that the people who do Transformation are bad people or bad at their jobs - they are only doing the best they can under the circumstances. It is the circumstances (their artefacts) that are of insufficient maturity.

All these traits create serious knock on problems as the hidden mess and confusion can easily hide many errors and inconsistencies of varying degrees from small to monumentally important. It is not a case of IF these errors and inconsistencies will be discovered, it's just a question of WHEN.

Without increasing our maturity in how we represent and store this information, it is impossible to find these errors and inconsistencies when the work is done to create them - the right time. Therefore these errors and inconsistencies will be tripped over later on in project execution when much time, effort and money has been spent and therefore wasted.

We need to take a more mature approach to the Artefacts used.




2008-2016 Pragmatic EA Ltd