<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	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/"
		>
<channel>
	<title>Comments for John Levy Consulting</title>
	<atom:link href="http://johnlevyconsulting.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://johnlevyconsulting.com</link>
	<description>High-tech management and IT business alignment for corporate executives</description>
	<lastBuildDate>Wed, 11 Jan 2012 00:52:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on How can IT management fail to understand business goals? by John Levy</title>
		<link>http://johnlevyconsulting.com/it-management-fails-to-understand-business-goals/#comment-10</link>
		<dc:creator>John Levy</dc:creator>
		<pubDate>Wed, 11 Jan 2012 00:52:30 +0000</pubDate>
		<guid isPermaLink="false">http://johnlevyconsulting.com/?p=714#comment-10</guid>
		<description>Thanks for the commentary, Robert.  

It&#039;s a long road to get metrics that do what IT needs and still represent real business objectives.  We have to start somewhere, so I recommend getting a much stronger dialogue going between the business sponsors and the IT service implementers.  And somewhere in that loop the IT management should be listening and contributing, too.  In my mind, Agile is all about having those dialogues active and effective while maintaining a disciplined development and operational environment.</description>
		<content:encoded><![CDATA[<p>Thanks for the commentary, Robert.  </p>
<p>It&#8217;s a long road to get metrics that do what IT needs and still represent real business objectives.  We have to start somewhere, so I recommend getting a much stronger dialogue going between the business sponsors and the IT service implementers.  And somewhere in that loop the IT management should be listening and contributing, too.  In my mind, Agile is all about having those dialogues active and effective while maintaining a disciplined development and operational environment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on How can IT management fail to understand business goals? by Robert Keahey</title>
		<link>http://johnlevyconsulting.com/it-management-fails-to-understand-business-goals/#comment-9</link>
		<dc:creator>Robert Keahey</dc:creator>
		<pubDate>Wed, 11 Jan 2012 00:35:40 +0000</pubDate>
		<guid isPermaLink="false">http://johnlevyconsulting.com/?p=714#comment-9</guid>
		<description>John,

Very interesting perspectives. You have definitely hit on some of the key contributors to the misalignment. 

This is an interesting problem, dating back to the very early days of &quot;IT&quot;. Remember 6-9 month (or even longer...) development and release cycles? By the time new capabilities were ready they were already out of sync with the business needs. And we weren&#039;t even living in the age of &quot;web speed&quot;. 

Fast forward through the years and the problem remained, but the drivers of misalignment changed. We learned that client/server and the internet/web gave us more flexibility, but it also gave us sprawl and complexity. And all those old systems now became &quot;legacy maintenance&quot; costs, eating into the IT budgets as you mentioned.

Now we&#039;re in the age of cloud computing, and the situation remains basically the same. We now have layers of legacy - all that client/server and internet/web stuff is now piling on. We have more sprawl - both physical and virtual. And, as we spoke about last week, we now have &quot;C4&quot; (credit card cloud computing), with the potential to cause a significant explosion in the business model. And as we all know, IT will have to fix the problem. 

Moving at &quot;web speed&quot; is good, but as you mentioned, not being able to measure the impact of all the elements that make up your product/service supply chain creates a lot of finger pointing when things go bad, and even when they don&#039;t in some cases. The key, and I applaud your insight on this point, is to link the value and the measurement of IT to the business drivers and success factors. While measuring cost per MIP or cost per terabyte of data stored is interesting, it provides little value in determining if IT is adding to or detracting from the performance of the lines of business. Determining which factors are important and can be linked needs to start way up front in the planning process. All too often we design a solution and then go back and try to figure out how IT impacts its performance. Rarely works.

But the real trick, and I&#039;m interested in hearing your thoughts on this, is how you instill a sense of discipline and reasonable control in defining these relationships in the age of &quot;agile&quot; development. Not an easy task by any means...</description>
		<content:encoded><![CDATA[<p>John,</p>
<p>Very interesting perspectives. You have definitely hit on some of the key contributors to the misalignment. </p>
<p>This is an interesting problem, dating back to the very early days of &#8220;IT&#8221;. Remember 6-9 month (or even longer&#8230;) development and release cycles? By the time new capabilities were ready they were already out of sync with the business needs. And we weren&#8217;t even living in the age of &#8220;web speed&#8221;. </p>
<p>Fast forward through the years and the problem remained, but the drivers of misalignment changed. We learned that client/server and the internet/web gave us more flexibility, but it also gave us sprawl and complexity. And all those old systems now became &#8220;legacy maintenance&#8221; costs, eating into the IT budgets as you mentioned.</p>
<p>Now we&#8217;re in the age of cloud computing, and the situation remains basically the same. We now have layers of legacy &#8211; all that client/server and internet/web stuff is now piling on. We have more sprawl &#8211; both physical and virtual. And, as we spoke about last week, we now have &#8220;C4&#8243; (credit card cloud computing), with the potential to cause a significant explosion in the business model. And as we all know, IT will have to fix the problem. </p>
<p>Moving at &#8220;web speed&#8221; is good, but as you mentioned, not being able to measure the impact of all the elements that make up your product/service supply chain creates a lot of finger pointing when things go bad, and even when they don&#8217;t in some cases. The key, and I applaud your insight on this point, is to link the value and the measurement of IT to the business drivers and success factors. While measuring cost per MIP or cost per terabyte of data stored is interesting, it provides little value in determining if IT is adding to or detracting from the performance of the lines of business. Determining which factors are important and can be linked needs to start way up front in the planning process. All too often we design a solution and then go back and try to figure out how IT impacts its performance. Rarely works.</p>
<p>But the real trick, and I&#8217;m interested in hearing your thoughts on this, is how you instill a sense of discipline and reasonable control in defining these relationships in the age of &#8220;agile&#8221; development. Not an easy task by any means&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

