How was Training?

more

Very good! The course gave me a great understanding of EA and how it is different from EITA. - ESB Manager/Senior Systems Developer II, PPDI, USA, Sep 2010

Recommend PEAF?

more

Yes - Ontology - IT Architect, KPN Telecom, Netherlands, Jan 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  

Desktop

Mobile

 

<< Previous <<

>> Next >>

Any framework will never be 100% correct for 100% of Enterprises. Therefore, it is reasonable for users of frameworks to view them in terms of adopting and levering what works for them. This is generally accepted. The question is, how?

The X-Frameworks and Ontologies illustrate the way an Enterprise can use the Pragmatic Frameworks - To use them as a basis to create their own Enterprise specific frameworks (X-Framework) by taking a Pragmatic Framework (or Ontology) and making the necessary changes required, in terms of content, branding, naming etc. The "X" is used as a placeholder that is meant to be replaced by an acronym specific to your Enterprise.

Most other frameworks only provide the absolute minimum help (generally nothing!) to adopt them for two main reasons:

      Tailoring - Firstly, in terms of being able to tailor a framework to your Enterprise so that it becomes your framework. This is usually because framework providers do not want to give you their "crown jewels". Doing so would enable you as an End-User Organisation to do a lot of the work yourself, without the need to spend large amounts of money on external consultants to do so.

      Adoption - Secondly, in terms of levels of maturity and how to go about adopting the framework. Again, this is usually because framework providers do not want to give Enterprises those things because if they did then those Enterprise could adopt them with much less "help" from outside consultancies.

Pragmatic takes a distinctly different view by being committed to providing as much collateral and guidance as possible, in order to keep the money spent on external consultants (including our own!) to a minimum, in addition to reducing the risk of failure.

The Pragmatic way for an Enterprise to adopt any framework (and thereby increase its maturity in a particular domain) is for that Enterprise to do so themselves (perhaps supported by an external consultant operating in a supporting, mentoring and facilitating role) rather than something a consultancy comes in and does "to you".

We absolutely understand that most of the time peoples "day jobs" do not allow them to spend time modifying and adopting a framework, but we believe that rather than allowing your existing staff to continue 100% with their "day job" and then paying consultants to come in and "do it to you", a better use of resources is to pay consultants to backfill your existing people (if required), to free some of their time to allow them to modify and adopting the framework (possibly supported by an external consultant).

 

What Frameworks have you adopted (or tried to adopt) in the past?

How easy was it?

How much help and guidance was provided "out of the box"?

How easy was it to modify and augment the framework?

How much consultancy time and money was required?

Was the adoption successful?

 







 

2008-2016 Pragmatic EA Ltd