How was Training?


great first touch - Senior consultant, AutoCont, Czech Republic, Mar 2011

Recommend PEAF?


Yes - It is worth consideration - Solution Manager, Atos, UK, Jan 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  




<< Previous <<

>> Next >>

Like many things, these Frameworks have grown and evolved organically and expanded their scope and areas of interest as they themselves have matured. This usually happens when the framework creators realise that the problems being experienced within their domain, are being caused by immaturity in another domain (usually upstream) and therefore grow and seep into that domain to "fix" those problems. ITIL is a prime example of this.

How successful frameworks have been in morphing themselves into areas they were never designed to operate in is largely subjective, and opinion tends to be driven by allegiances and crusades. In addition all of these Frameworks have been designed and built in isolation - to optimise specific parts rather than the whole.

So, the problem is not the lack of frameworks. The problem is the abundance of frameworks. Because of this, there are overlaps, gaps, inconsistencies and clashes. In short, total confusion. So the framework providers, whose primary aim is to provide clarity in their domain, have created confusion in the wider domain.

Consequently people have adopted these frameworks in a similarly haphazard fashion, optimising specific parts but never considering the whole. Perhaps starting in one area and then finding themselves being subtly pulled into other areas. They have been optimising the parts at the expense of the whole.


2008-2016 Pragmatic EA Ltd