tag:blogger.com,1999:blog-6106782.post9159555718155737605..comments2024-03-27T10:47:33.255+00:00Comments on Architecture, Data and Intelligence: Enterprise Architect - Joke or Joker?Richard Veryardhttp://www.blogger.com/profile/04499123397533975655noreply@blogger.comBlogger6125tag:blogger.com,1999:blog-6106782.post-63851549622280620332008-08-12T19:29:00.000+01:002008-08-12T19:29:00.000+01:00In a later post on Enterprise Architecture and Han...In a later post on <A HREF="http://duckdown.blogspot.com/2008/08/enterprise-architecture-and-hand-waving.html" REL="nofollow">Enterprise Architecture and Hand Waving</A>, James McGovern suggests that the enterprise architect's use of PowerPoint is akin to a Jedi mind trick. Transformation and personal mastery then - enterprise architects who practise these skills are indeed from the planet Pluto.Richard Veryardhttps://www.blogger.com/profile/04499123397533975655noreply@blogger.comtag:blogger.com,1999:blog-6106782.post-73700675461389239552008-07-18T21:21:00.000+01:002008-07-18T21:21:00.000+01:00Hi Richard,I do agree, who is going to pull all th...Hi Richard,<BR/><BR/>I do agree, who is going to pull all the roles together and ensure that they are aligned?<BR/><BR/>Well I think that answer is by turning EA into a practice, like Software Development has the SDLC where everyone roughly now knows their role and their place in it. Thanks to Agile development the SDLC isn't linear either. So lessons can be learnt there.<BR/><BR/>Funny thing is that I think that TOGAF 8 actually hints at this with the various stages of the ADM, I have notice this in my organistion where people nature lean to a particular part.<BR/><BR/>Anyway this is a debate that can rage and rage but I sincerely wish that it can be done in a mature and constructive way which sadly I have seen the opposite in some instances. At the end of the day it's not worth getting to emotive over. Pull yourselves together people!David Oliverhttps://www.blogger.com/profile/11894760937076117103noreply@blogger.comtag:blogger.com,1999:blog-6106782.post-21884089781338076532008-07-17T02:04:00.000+01:002008-07-17T02:04:00.000+01:00Hi Dave. There are certainly different skills (and...Hi Dave. There are certainly different skills (and perhaps personality types) needed on an EA team. I used a cheap metaphor (Mars, Venus, and so on) - for a more scientific analysis you could look at something like <A HREF="http://en.wikipedia.org/wiki/Belbin_Team_Inventory" REL="nofollow">Belbin's team inventory</A>. <BR/><BR/>But I'd be wary of dividing EA into separate roles or teams with separate responsibilities for different aspects of EA. Because then who is going to put the pieces back together? Surely the overall coordination and alignment between the constituent parts of EA (whatever they are) is the <A HREF="http://en.wikipedia.org/wiki/Keystone_(architecture)" REL="nofollow">keystone</A> of EA.Richard Veryardhttps://www.blogger.com/profile/04499123397533975655noreply@blogger.comtag:blogger.com,1999:blog-6106782.post-13952905681571211272008-07-16T22:01:00.000+01:002008-07-16T22:01:00.000+01:00Hi Richard,Very interesting thoughts, I would love...Hi Richard,<BR/><BR/>Very interesting thoughts, I would love to discuss them with you. I believe that Enterprise Architecture is really a whole set of roles.<BR/><BR/>Like any person doing more than one job they aren't going to any job well. I think we as an industry need to recognise that and then start to break up EA into it's constituant parts. This will then have a knock-on effect of more visible benefit and better tools.<BR/><BR/>What do you think?<BR/><BR/>Best Regards,<BR/><BR/>Dave OliverDavid Oliverhttps://www.blogger.com/profile/11894760937076117103noreply@blogger.comtag:blogger.com,1999:blog-6106782.post-86832936261250111942008-07-13T12:10:00.000+01:002008-07-13T12:10:00.000+01:00Hello Guilhem. I'm sorry you didn't understand or ...Hello Guilhem. I'm sorry you didn't understand or appreciate my post. If you had managed to read more of my blog, you might have picked up a different opinion on "technology initiatives".<BR/><BR/>See my later post <A HREF="http://rvsoapbox.blogspot.com/2008/07/strategy-isnt-direction.html" REL="nofollow">Strategy isn't a Direction</A>Richard Veryardhttps://www.blogger.com/profile/04499123397533975655noreply@blogger.comtag:blogger.com,1999:blog-6106782.post-26330497242792845882008-07-13T02:01:00.000+01:002008-07-13T02:01:00.000+01:00wowow what a load of bullshit! i am sure you are t...wowow what a load of bullshit! i am sure you are the kind of guy who enjoys driving strategic direction through technology initiatives.Anonymousnoreply@blogger.com