<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Banky For President &#187; IT Strategy</title>
	<atom:link href="http://www.bankyforpresident.com/category/it-strategy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.bankyforpresident.com</link>
	<description>By The People, For the People . . .</description>
	<lastBuildDate>Wed, 13 May 2009 15:09:49 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>On Architecture . . .</title>
		<link>http://www.bankyforpresident.com/2008/04/16/on-architecture/</link>
		<comments>http://www.bankyforpresident.com/2008/04/16/on-architecture/#comments</comments>
		<pubDate>Wed, 16 Apr 2008 16:09:30 +0000</pubDate>
		<dc:creator>Banky</dc:creator>
				<category><![CDATA[IT Strategy]]></category>
		<category><![CDATA[architecture]]></category>
		<category><![CDATA[enlightenment]]></category>
		<category><![CDATA[evolution]]></category>
		<category><![CDATA[lightthread]]></category>

		<guid isPermaLink="false">http://www.bankyforpresident.com/2008/04/16/on-architecture/</guid>
		<description><![CDATA[The most confusing role within an IT organization is the Architect. Most people aren&#8217;t really sure what they do.  And there is a really good reason for that.
There are lots of really bad architects.
A good architect is part guardian, part ninja, part wizard, part consigliere and usually very very charming (okay maybe only in [...]]]></description>
			<content:encoded><![CDATA[<p>The most confusing role within an IT organization is the Architect. Most people aren&#8217;t really sure what they do.  And there is a really good reason for that.</p>
<p>There are lots of really bad architects.</p>
<p>A good architect is part guardian, part ninja, part wizard, part <a href="http://en.wikipedia.org/wiki/Consigliere" title="The Genco Abandando of IT">consigliere</a> and usually very very charming (okay maybe only in my case).  They act on behalf of IT and the company to keep costs low but capability high.  They are the strategy arm of IT and as such, they make recommendations that steer the company&#8217;s technical capabilities for the future and beyond.</p>
<p>I work in a fairly evolved IT organization.  Part of being enlightened is knowing that you aren&#8217;t and, as an organization, we know enough to know our strengths and weaknesses.  I recently visited with another IT organization that is a bit farther down the pyramid of <a href="http://en.wikipedia.org/wiki/Maslow's_hierarchy_of_needs">Maslow&#8217;s hierarchy of human needs</a>. They aren&#8217;t sure what their architects do.  They invite the architects to meetings but they never show up.  They visit the architects, ask them to make recommendations on moving forward and never hear back from them.  As such, software gets built and there is no governance available to ensure code is re-used, or can be re-used in the future. And there is  NO process for the architects to act as a checkpoint as software moves throughout its lifecycle.</p>
<p>So the architects sit around and wonder why won&#8217;t anyone listen to them. . .</p>
<p>The best architects don&#8217;t sit around and wait for people to come to them.  They insert themselves into the process.  They are in people&#8217;s faces wondering why they coded something one way when they were EXPLICITLY told to code it another.  They remind the business to go focus on functionality and to let the architect worry about solutions.  They act as counsel to the Account Managers of IT to educate them on what the horizontal solutions for the company are so that they can explain them to the business.  The architects also recommend to the CIO where money can be saved and create plans for how that savings can occur for the next 2-5 years.</p>
<p>Remember, respect isn&#8217;t given, it&#8217;s earned. Just because you have the cool title, doesn&#8217;t mean people are going to fall down at your feet and ask for your opinion.  If you want someone to hear your opinion, you might try giving it.</p>
<p>In short, Architects need to be the smartest people in the room.  And good architects know they are.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.bankyforpresident.com/2008/04/16/on-architecture/feed/</wfw:commentRss>
		<slash:comments>1</slash:comments>
		</item>
	</channel>
</rss>
