<?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>architectbootcamp.com &#187; future state architecture</title>
	<atom:link href="http://architectbootcamp.com/tag/future-state-architecture/feed/" rel="self" type="application/rss+xml" />
	<link>http://architectbootcamp.com</link>
	<description>Promoting Information Architecture Excellence</description>
	<lastBuildDate>Mon, 19 Dec 2011 16:27:47 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Chief Architect&#8217;s Big Three Secrets for Enterprise Architecture Planning</title>
		<link>http://architectbootcamp.com/enterprise-architecture/chief-architects-big-three-secrets-eap/</link>
		<comments>http://architectbootcamp.com/enterprise-architecture/chief-architects-big-three-secrets-eap/#comments</comments>
		<pubDate>Wed, 19 Aug 2009 18:38:28 +0000</pubDate>
		<dc:creator>superfli</dc:creator>
				<category><![CDATA[chief architect]]></category>
		<category><![CDATA[Enterprise architecture]]></category>
		<category><![CDATA[Role]]></category>
		<category><![CDATA[architect role]]></category>
		<category><![CDATA[enterprise architecture planning]]></category>
		<category><![CDATA[enterprise portfolio mana]]></category>
		<category><![CDATA[future state architecture]]></category>

		<guid isPermaLink="false">http://architectbootcamp.com/?p=504</guid>
		<description><![CDATA[In a previous article, the spotlight fell on three biggest risks the Chief Architect needs to manage before moving onto something less tactical.  Consider now the area of strategic planning and opportunities in your future state landscape.  Three key sources that the chief architect needs to explore are: CEO’s Top Strategic Drivers CIO’s Primary Concerns [...]]]></description>
			<content:encoded><![CDATA[<p>In a previous article, the spotlight fell on three biggest risks the Chief Architect needs to manage before moving onto something less tactical.  Consider now the area of strategic planning and opportunities in your future state landscape.  Three key sources that the chief architect needs to explore are:</p>
<ol>
<li>CEO’s Top Strategic      Drivers</li>
<li>CIO’s Primary Concerns</li>
<li>Enterprise Portfolio      Management</li>
</ol>
<p>In fact, the CEO owns, knows, eats and breathes their top three strategic drivers.  At a time in the economy that we are facing now pure survival may likely be their number one focus.  Such drivers might include the area cost savings, as well company stock prices.  The chief architect needs to fully understand how these drivers impact or are impacted by the Enterprise Architecture Plan.</p>
<div id="attachment_506" class="wp-caption alignleft" style="width: 123px"><a href="http://www.architectbootcamp.com"><img class="size-full wp-image-506" title="strategic plannng" src="http://architectbootcamp.com/wp-content/uploads/2009/08/man-with-map.jpg" alt="Figuring our which way to go" width="113" height="170" /></a><p class="wp-caption-text">Figure out plan of attack</p></div>
<p>Choices made in the areas of infrastructure and solutions will most likely be efficiency based, and risk averse.  Creatively considering ways in which the architecture can contribute in the area of competitive tactics is another way in which we can provide value.  If the CEO is really focused on their competition’s moves, it might be a looming takeover or collapse.  How can the strategic plan allow for agility in these types of circumstances?  What would it take to expend with a line? A division?  Or purchase either?</p>
<p>An additional area of CEO concern is major projects.  The CEO realistically needs to keep aware of the biggest corporate expenditures and these may be IT projects.  Characteristically these are very high profile projects or large replacement projects.  The chief architect should be fully aware of what the CEO&#8217;s concerns are, and what it is troubling them about the projects.  It may be the board’s opinion of the project, or where else the money could be better spent.</p>
<p>The second area the chief architect needs to focus on is the concerns of the CIO.  It is crucial to have a list of things that keeps this soul up at night as well.  Some risky hardware component or some recent security lapse could be top of the list. It might be an employee or staffing issue.  Where they are privy, the chief architect needs to explore what can be done in upcoming plans.</p>
<p>Ultimately there is the major issue of job retention as a CIO.  Budget cuts and less than stellar IT performance can be used as stimulus to look within the large resource pool available.  What can be done to ensure IT performance is not a factor.</p>
<p>A major area of concern to the chief architect should always be enterprise portfolio management.  This is the prime source of where strategic future directives will be exposed.  The architect needs to comprehend and be fully aware at all times of the biggest opportunities.  What was the biggest project or investment identified?  What is on that list or that requires the biggest investment AS WELL as the biggest return on investment.</p>
<p>I would suggest that the chief architect to quickly scan that portfolio management list on a monthly basis and retain a list of the quick wins and low hanging fruit.  Each of these should be incorporated into whatever future planning is being pursued as the opportunities are available.</p>
<p>You&#8217;ve got to keep the pulse on these critical elements – and keep this in on your laser focus.  Continually update your enterprise architecture plan where you can whenever these strategic drivers change.</p>
<p>Happy Architecting</p>
<p>Sharon</p>
]]></content:encoded>
			<wfw:commentRss>http://architectbootcamp.com/enterprise-architecture/chief-architects-big-three-secrets-eap/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Basic Architecture Process &#8211; Part 2</title>
		<link>http://architectbootcamp.com/frameworks-process/basic-architecture-process-part-2/</link>
		<comments>http://architectbootcamp.com/frameworks-process/basic-architecture-process-part-2/#comments</comments>
		<pubDate>Sat, 17 Jan 2009 09:33:35 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Frameworks & Process]]></category>
		<category><![CDATA[basic architecture proces]]></category>
		<category><![CDATA[current state architectur]]></category>
		<category><![CDATA[future state architecture]]></category>
		<category><![CDATA[IT architect skill]]></category>
		<category><![CDATA[IT architecture process]]></category>

		<guid isPermaLink="false">http://enterprisearchitecturecoach.com/?p=83</guid>
		<description><![CDATA[We will go across the varying horizontal layers in a vertical fashion creating models or adding notes and analyzing the various components in order to achieve our target state. The nature or outcome of this process from moving the system towards the evolving to be state or]]></description>
			<content:encoded><![CDATA[<p><span style="font-size: 10pt">We will go across the varying horizontal layers in a vertical fashion creating models or adding notes and analyzing the various components in order to achieve our target state. The nature or outcome of this process from moving the system towards the evolving to be state or </span></p>
]]></content:encoded>
			<wfw:commentRss>http://architectbootcamp.com/frameworks-process/basic-architecture-process-part-2/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>3 Keys to Future State Architecture</title>
		<link>http://architectbootcamp.com/enterprise-architecture/3-keys-to-future-state-architecture/</link>
		<comments>http://architectbootcamp.com/enterprise-architecture/3-keys-to-future-state-architecture/#comments</comments>
		<pubDate>Fri, 31 Oct 2008 09:54:03 +0000</pubDate>
		<dc:creator></dc:creator>
				<category><![CDATA[Enterprise architecture]]></category>
		<category><![CDATA[business driver]]></category>
		<category><![CDATA[future architecture]]></category>
		<category><![CDATA[future state architecture]]></category>
		<category><![CDATA[strategic direction]]></category>
		<category><![CDATA[strategic driver]]></category>

		<guid isPermaLink="false">http://enterprisearchitecturecoach.com/?p=96</guid>
		<description><![CDATA[Do You Have a Crystal Ball:Ã‚Â 3 Future State Architecture Keys to Make them Think So! Documenting the current state architecture is a must to any enterprise or system architecture report, and even though we understand this, itÃ¢â‚¬â„¢s the future state that everyone is anxious to see and share.Ã‚Â LetÃ¢â‚¬â„¢s face it Ã¢â‚¬â€œ they are also waiting [...]]]></description>
			<content:encoded><![CDATA[<p style="text-align: justify;"><strong>Do You Have a Crystal Ball:Ã‚Â 3 Future State Architecture Keys to Make them Think So!</strong></p>
<div style="text-align: justify;">Documenting the current state architecture is a must to any enterprise or system architecture report, and even though we understand this, itÃ¢â‚¬â„¢s the future state that everyone is anxious to see and share.Ã‚Â LetÃ¢â‚¬â„¢s face it Ã¢â‚¬â€œ they are also waiting to critique it.Ã‚Â There are components of a future architecture that make or break its impending success Ã¢â‚¬â€œ or failure.Ã‚Â In todayÃ¢â‚¬â„¢s Abstract, I want</div>
]]></content:encoded>
			<wfw:commentRss>http://architectbootcamp.com/enterprise-architecture/3-keys-to-future-state-architecture/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

