|
|
What we need in an architect...and everyone else
belongs to Blogs   by Steve Elmore on May 22, 2008 - 04:21 PM read 828 times |
There is an excellent article in the Architecture Journal: the A-Z Guide to Being an Architect. Good advice for us all.
A Is for Advocate
"I think you'll find that you really don't want to do it like that."
Architects have to explain and advise on technical issues to business stakeholders. They also have to be able to advise delivery teams on how to build. This advice is the currency of an architect; invested wisely, it will return goodwill and trust. The architect is asked for advice, because it is the architect's job to "see the whole."
-
re: What we need in an architect...and everyone else
a reply to What we need in an architect...and everyone else
by 'Bayo Akinola-Odusola on May 23, 2008 - 04:42 PM read 83 timesOver the years I have worked as a Business Architect on various client development and product launch projects and this is indeed very true in respect to being pivotal.
Explaining and advising on business operational and integration issues to business stakeholders at different levels of authority and knowledge can be tricky business. My colleagues in the IT Development, Delivery and Operations teams have the power to make things easier or muddy the waters.
Prudent and "timely" advice is without a doubt, the best trading currency that has always existed and will exist for as long as Architects exist. As Business and Technical Architects we're trusted for advice primarily because, as stated, it's our role "see, interpret and detail" that bigger picture organizations have or may be striving to bring to life.
Featured
Author Profile
Subscribe
Feed for nGenera Community:
Public
Secure
Why subscribe? What is RSS?