I new appointment for a Client Architect has just come over my desk, mmmm so what does a Client Architect do? According to the memo, a Client Architect:
- Leadership of the infrastructure architecture
- Representative in the infrastructure architecture community
- Rationalising and resolving multiple potentially competing technical priorities
- Manage and lead the development of project architectures
So what is the difference between this and a Solution Architect or an Infrastructure Architect. As a community we can’t bo doing ourselves any favours when we invent roles which don’t really add any value. Within our team we have five(5) types of Architects and we still haven’t agreement on who is responsible for what. As per the title of this blog it is hard enough to define what an architect is let alone all the different specific architect types we seem to like to create.
Tags: Architecture
7 March 2008 at 9:51 am |
[...] having at work is the value of having so may different types of Architects. I blogged about the new Client Architect role we were creating and my thought on that. Well the conversation is moving the other way where [...]
7 March 2008 at 12:18 pm |
Same feelings about the “Solution Orchestrator” then?…