Enterprise Architecture

A Pragmatic Approach Using PEAF

Buy










◄◄◄ Previous Page         

.  

          Next Page ►►►

Regarding EA Frameworks, we have adopted TOGAF but it falls short in a number of important respects. For example:

1)    It plays more a political box ticking part rather than actually using it.

2)    It is extremely detailed and difficult to understand let alone adopt

3)    It doesn’t really apply to EA (the work we need to do BEFORE we start executing projects).

4)    Training provided was inadequate.

5)    We were not given any time to adopt it, i.e. use it to change the Methods, Artefacts, Culture and Environment we use to effect EA work.

Regarding EA Tools, we have adopted various tools but they fall short in a number of important respects. For example:

1)    They only allow us to draw models, not perform the analyses we need.

2)    The don’t allow us to build multiple scenarios and compare them.

3)    Ownership and Maintenance of the information goes through 1 person creating a massive bottleneck.

4)    Training provided was inadequate.

5)    When we populate the model with information, we do not perform a proper quality evaluation on it and so end up populating the models with incorrect information.

6)    When we populate the model with information, we do not remove the source of that information, which means we only add to the data maintenance headache.

 

Questions to ponder...

Do these generic issues (relating to the framework and technology Environment used for EA) apply to your Enterprise?

What specific issues (relating to the framework and technology Environment used for EA) apply to your Enterprise?

◄◄◄ Previous Page          

          Next Page ►►►


 

© 2008-2019 Pragmatic EA Ltd