This week I find a question that has been bobbling around my head is… “Is there such a thing as a junior Enterprise Architect?”
If there is, in what way is it junior… scope?… experience?… ability?… breadth?…
In many ways, an Enterprise Architect is often percieved as being highly experienced, enterprise-wide in their perspective, able to communicate to Senior Management equally as well as Development Teams, knowledgeable across a wide number of technologies and domains… so how do you get to that somewhat formidable state? If you limit domains or scope, a Junior EAer becomes a Project Architect or Data Architect say, and if you limit ability or experience – how can they practice EA?
Perhaps instead it is the question that is wrong…. or more specifically, does it work if we change it to … “Is there such a thing as a junior Enterprise Architetcure Practitioner?”
Thoughts?
December 20, 2007 at 6:49 pm |
[...] Junior Enterprise Architect? [...]
December 22, 2007 at 2:13 pm |
[...] second post on Junior Enterprise Architect resonates with me as I am new to the practice, however at the tender age of 37 I’m not sure [...]
July 20, 2008 at 12:31 am |
[...] second post on Junior Enterprise Architect resonates with me as I am new to the practice, however at the tender age of 37 I’m not sure [...]
August 19, 2008 at 9:38 pm |
I consider myself a Junior Enterprise Architect… I am limited in experience and come from more of an Infrastructure background than development, but I have the skills necessary to articulate strategy to management and implementation to the technical teams.
I believe the Junior comes into play as to the size of the enterprise we architect. I work for a mid-sized manufacturer, typically not associated with having an enterprise architecture program at all. I find that I need to fill in my gaps of knowledge by relying on subject matter experts in development and data when I need them and focusing on applying consistent principles to the decisions to achieve our goals.