<?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 The Highlander Principle</title>
	<atom:link href="http://www.highlanderprinciple.com/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.highlanderprinciple.com</link>
	<description>One IT Architecture</description>
	<lastBuildDate>Wed, 09 Dec 2009 14:56:39 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.6</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>Comment on Do we really need an IT Risk Control Department? by David Lodge</title>
		<link>http://www.highlanderprinciple.com/2009/11/do-we-really-need-a-it-risk-control-department/comment-page-1/#comment-90</link>
		<dc:creator>David Lodge</dc:creator>
		<pubDate>Wed, 09 Dec 2009 14:56:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=205#comment-90</guid>
		<description>I think the question is less whether we need an IT Risk Control function, but what the function looks like and how it operates. Most companies I&#039;ve seen operate a 3 line of defence model (Function, independent risk, and audit) but they work to different objectives.

I am a risk controller by profession, and can see real benefit in controlling IT risk with a thorough understanding of the IT Function (CIO) and Business objectives. With these in mind, risk decisions can be taken with a real understanding of the implications such decisions will have on driving the business forward and the trade offs that must be considered. IT Risk is, afterall, Business risk.

However, if IT Risk decisions are taken only considering a single IT risk factor (IT Security say) then the likely implication is that the IT function and business will be constrained in other ways.</description>
		<content:encoded><![CDATA[<p>I think the question is less whether we need an IT Risk Control function, but what the function looks like and how it operates. Most companies I&#8217;ve seen operate a 3 line of defence model (Function, independent risk, and audit) but they work to different objectives.</p>
<p>I am a risk controller by profession, and can see real benefit in controlling IT risk with a thorough understanding of the IT Function (CIO) and Business objectives. With these in mind, risk decisions can be taken with a real understanding of the implications such decisions will have on driving the business forward and the trade offs that must be considered. IT Risk is, afterall, Business risk.</p>
<p>However, if IT Risk decisions are taken only considering a single IT risk factor (IT Security say) then the likely implication is that the IT function and business will be constrained in other ways.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on VMware vSphere v Microsoft HyperV by Tweets that mention VMware vSphere v Microsoft HyperV &#124; The Highlander Principle -- Topsy.com</title>
		<link>http://www.highlanderprinciple.com/2009/10/vmware-vsphere-v-microsoft-hyperv/comment-page-1/#comment-69</link>
		<dc:creator>Tweets that mention VMware vSphere v Microsoft HyperV &#124; The Highlander Principle -- Topsy.com</dc:creator>
		<pubDate>Tue, 17 Nov 2009 18:01:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=141#comment-69</guid>
		<description>[...] This post was mentioned on Twitter by Steve O&#039;Donnell, markbowker. markbowker said: RT @stephenodonnell: VMware vSphere v Microsoft HyperV interesting TCO article - http://bit.ly/9cytg &lt;- All fair points [...]</description>
		<content:encoded><![CDATA[<p>[...] This post was mentioned on Twitter by Steve O&#39;Donnell, markbowker. markbowker said: RT @stephenodonnell: VMware vSphere v Microsoft HyperV interesting TCO article &#8211; <a href="http://bit.ly/9cytg" rel="nofollow">http://bit.ly/9cytg</a> &lt;- All fair points [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on DataCenter Buzzword Bingo by Steve O'Donnell</title>
		<link>http://www.highlanderprinciple.com/2009/11/datacenter-buzzword-bingo/comment-page-1/#comment-68</link>
		<dc:creator>Steve O'Donnell</dc:creator>
		<pubDate>Tue, 17 Nov 2009 08:14:19 +0000</pubDate>
		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=191#comment-68</guid>
		<description>Lossless Ethernet
Network Attached Storage
Block Storage
Fibre Channel Storage
FCIP - Fibre Channel over IP
Object Storage
Cloud Storage (AKA Object Storage)
Chunk Mirroring</description>
		<content:encoded><![CDATA[<p>Lossless Ethernet<br />
Network Attached Storage<br />
Block Storage<br />
Fibre Channel Storage<br />
FCIP &#8211; Fibre Channel over IP<br />
Object Storage<br />
Cloud Storage (AKA Object Storage)<br />
Chunk Mirroring</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Cisco Unified Computing by Eric Cantona</title>
		<link>http://www.highlanderprinciple.com/2009/06/cisco-unified-computing/comment-page-1/#comment-26</link>
		<dc:creator>Eric Cantona</dc:creator>
		<pubDate>Wed, 01 Jul 2009 15:25:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=54#comment-26</guid>
		<description>Interesting observation. UCS will inevitably offer organisational re-org oppurtunities. One suspects that whilst the engineering and architecture will cross team boundaries, Platform, Networks, Virtualistion etc it&#039;s where the solution ends up being run operationally thats compelling.

Will UCS fall in to a platform operations function as many beleive or spawn a whole new department?

Also If organisations dont fully adopt UCS tranditional rack and blade process will need to be maintained - so will the ROI stack up.

An interesting and exciting new technology....one to be close to and watch how it progresses</description>
		<content:encoded><![CDATA[<p>Interesting observation. UCS will inevitably offer organisational re-org oppurtunities. One suspects that whilst the engineering and architecture will cross team boundaries, Platform, Networks, Virtualistion etc it&#8217;s where the solution ends up being run operationally thats compelling.</p>
<p>Will UCS fall in to a platform operations function as many beleive or spawn a whole new department?</p>
<p>Also If organisations dont fully adopt UCS tranditional rack and blade process will need to be maintained &#8211; so will the ROI stack up.</p>
<p>An interesting and exciting new technology&#8230;.one to be close to and watch how it progresses</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Quality, Cost or Time? by Steve O'Donnell</title>
		<link>http://www.highlanderprinciple.com/2008/08/quality-cost-or-time/comment-page-1/#comment-2</link>
		<dc:creator>Steve O'Donnell</dc:creator>
		<pubDate>Mon, 29 Sep 2008 11:55:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.highlanderprinciple.com/?p=11#comment-2</guid>
		<description>I think you are talking about me Mark? The other important point is that we need to explain this relationship to everyone who wants to change one of the three. If you change requirements half way through it is likely to extend time and increase costs. If we run out of budget quality will slip...

A project usualy finishes the way it was started. If it is chaos at the start, guess what... Well initiated projects usually finish well.

Steve</description>
		<content:encoded><![CDATA[<p>I think you are talking about me Mark? The other important point is that we need to explain this relationship to everyone who wants to change one of the three. If you change requirements half way through it is likely to extend time and increase costs. If we run out of budget quality will slip&#8230;</p>
<p>A project usualy finishes the way it was started. If it is chaos at the start, guess what&#8230; Well initiated projects usually finish well.</p>
<p>Steve</p>
]]></content:encoded>
	</item>
</channel>
</rss>
