How was Training?

more

It's great to do a deep dive of framework materials - a course participant can always uncovers tidbits of value that are overlooked or minimized during the pressures of actual practice. - Enterprise Architect, Green Tree Services, USA, Aug 2013

Recommend PEAF?

more

Yes - More pragmatic, less academic and prescriptive. - chief architect/director, acting as contractor for many enterprises, UK, Jan 2015

  Introduction   Context   Methods   Artefacts   Culture   Environment   Adoption  

Desktop

Mobile







 

<< Previous <<

>> Next >>

The fourth main barrier to adoption is that we want to change a broken system of Transformation - specifically (from an EA perspective) we want to change the flawed Strategising and Roadmapping phases of Transformation.

But to get that work on the table we are generally faced with having to go through the Enterprises current (flawed) Strategising and Roadmapping phases.

This is why PEAF propose a separate adoption process that does not follow the organisations current process, but instead follows the more mature Transformation process defined by POET.

Of course, just because we define it does not mean that people will be able to follow it. We should therefore be cognizant of the fact that we will face a lot of pushback from an Enterprises current Strategising and Roadmapping capabilities.

 

Does your Enterprises current Strategising and Roadmapping capabilities, prevent them from seeing the benefit of improving them?

How can you get round that?

 

 

2008-2016 Pragmatic EA Ltd