Comments on: Lecturing on EA @ BCIT – Rethinking my Approach http://leodesousa.ca/2010/01/lecturing-on-ea-bcit-rethinking-my-approach/?utm_source=rss&utm_medium=rss&utm_campaign=lecturing-on-ea-bcit-rethinking-my-approach a practical approach by Leo de Sousa Wed, 08 Sep 2010 21:38:39 -0700 hourly 1 http://wordpress.org/?v=3.0.1 By: Leo de Sousa http://leodesousa.ca/2010/01/lecturing-on-ea-bcit-rethinking-my-approach/comment-page-1/#comment-2652 Leo de Sousa Wed, 24 Feb 2010 23:25:09 +0000 http://leodesousa.ca/?p=772#comment-2652 Allan, Thank you for the excellent insights and feedback. We do have a long way to go to get to the rigour that is demonstrated by Finance practices. Have you looked at what the Center for the Advancement of the Enterprise Architecture Practice (CAEAP) is up to. I have been working on a couple of chapters in the Professional Practice Guide. Here is the website http://caeap.org My presentation is too big to email but I can create a pdf to share with you. Cheers! Leo Allan,

Thank you for the excellent insights and feedback. We do have a long way to go to get to the rigour that is demonstrated by Finance practices. Have you looked at what the Center for the Advancement of the Enterprise Architecture Practice (CAEAP) is up to. I have been working on a couple of chapters in the Professional Practice Guide. Here is the website http://caeap.org

My presentation is too big to email but I can create a pdf to share with you.

Cheers! Leo

]]> By: Allan Gillard http://leodesousa.ca/2010/01/lecturing-on-ea-bcit-rethinking-my-approach/comment-page-1/#comment-2651 Allan Gillard Wed, 24 Feb 2010 23:13:56 +0000 http://leodesousa.ca/?p=772#comment-2651 Hi Leo, My view on this as an architect for over 15 years, and a developer before that, is that I would agree that much of Enterprise Architecture (EA) has a technical focus. I see that as a consequence of the increasing reliance on technology to enable the business to deliver its goods and services to its customers. Where EA is applied in an organisation tends to be centred around Projects - which makes sense since they are the change mechanism for taking an organisation from where they are today (the Current State), to where they want to be (the Target State). EA is about defining that Target State (across the Business, Information, Application and Technology domains) as determined by the Business Drivers and stated in the Business Strategy, and outlining the roadmap on how best to get there. The Business Strategy identifies the Business Objectives that are then assigned to Projects to deliver (the Demand Pipeline). Solution Architecture (SA) takes the roadmaps and applies them to the project objectives and constraints (Budget, Cost and Resources - the Supply Pipeline), and designs the solution in line with the specific project requirements. The solution is then developed and implemented by the project within the current operational and system management environment. The point is that EA is still an evolving practice when compared to the equivalent disicplines of Finance and HR - Finance has its roots going back to the 18th century, and HR practices dated from the late 19th century, while EA only really began in the 1960s. I would be interested if possible to get a copy of the notes from your presentation. Regards, Allan. Hi Leo,
My view on this as an architect for over 15 years, and a developer before that, is that I would agree that much of Enterprise Architecture (EA) has a technical focus. I see that as a consequence of the increasing reliance on technology to enable the business to deliver its goods and services to its customers.
Where EA is applied in an organisation tends to be centred around Projects – which makes sense since they are the change mechanism for taking an organisation from where they are today (the Current State), to where they want to be (the Target State). EA is about defining that Target State (across the Business, Information, Application and Technology domains) as determined by the Business Drivers and stated in the Business Strategy, and outlining the roadmap on how best to get there. The Business Strategy identifies the Business Objectives that are then assigned to Projects to deliver (the Demand Pipeline).
Solution Architecture (SA) takes the roadmaps and applies them to the project objectives and constraints (Budget, Cost and Resources – the Supply Pipeline), and designs the solution in line with the specific project requirements.
The solution is then developed and implemented by the project within the current operational and system management environment.
The point is that EA is still an evolving practice when compared to the equivalent disicplines of Finance and HR – Finance has its roots going back to the 18th century, and HR practices dated from the late 19th century, while EA only really began in the 1960s.
I would be interested if possible to get a copy of the notes from your presentation.
Regards,
Allan.

]]> By: Tweets that mention Enterprise Architecture in Higher Education » Lecturing on EA @ BCIT – Rethinking my Approach -- Topsy.com http://leodesousa.ca/2010/01/lecturing-on-ea-bcit-rethinking-my-approach/comment-page-1/#comment-2372 Tweets that mention Enterprise Architecture in Higher Education » Lecturing on EA @ BCIT – Rethinking my Approach -- Topsy.com Wed, 27 Jan 2010 18:21:52 +0000 http://leodesousa.ca/?p=772#comment-2372 [...] This post was mentioned on Twitter by Leo de Sousa, Fauzan Mohamad. Fauzan Mohamad said: EA: Enterprise Architecture in Higher Education » Lecturing on EA ...: Tonight, I had the privilege of being a gue... http://bit.ly/ag6q1f [...] [...] This post was mentioned on Twitter by Leo de Sousa, Fauzan Mohamad. Fauzan Mohamad said: EA: Enterprise Architecture in Higher Education » Lecturing on EA …: Tonight, I had the privilege of being a gue… http://bit.ly/ag6q1f [...]

]]> By: LeodeSousa http://leodesousa.ca/2010/01/lecturing-on-ea-bcit-rethinking-my-approach/comment-page-1/#comment-2371 LeodeSousa Wed, 27 Jan 2010 16:03:59 +0000 http://leodesousa.ca/?p=772#comment-2371 Early in the development of our EA practice, I spent most of my time listening in on meetings where there were pictures on the whiteboard. After a few of these meetings, the technical experts just expected the EA (me) to be there and started asking my opinion and advice. The other big win was embedding EA reviews into our Project Management and Change Management Processes. We were able to influence decisions on technology adoption and in some cases stopped projects altogether because we already had something that did what was required. Early in the development of our EA practice, I spent most of my time listening in on meetings where there were pictures on the whiteboard. After a few of these meetings, the technical experts just expected the EA (me) to be there and started asking my opinion and advice. The other big win was embedding EA reviews into our Project Management and Change Management Processes. We were able to influence decisions on technology adoption and in some cases stopped projects altogether because we already had something that did what was required.

]]> By: Mridul http://leodesousa.ca/2010/01/lecturing-on-ea-bcit-rethinking-my-approach/comment-page-1/#comment-2368 Mridul Wed, 27 Jan 2010 11:28:25 +0000 http://leodesousa.ca/?p=772#comment-2368 HI Leo, Just curious to know, how do you identify and put across short term benefits of EA, if any. And what is the time window for short term benefits? regards, Mridul HI Leo,
Just curious to know, how do you identify and put across short term benefits of EA, if any. And what is the time window for short term benefits?

regards,
Mridul

]]>