<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.itskeptic.org"  xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>The IT Skeptic - Comments for &quot;IT principles&quot;</title>
 <link>http://www.itskeptic.org/content/it-principles</link>
 <description>Comments for &quot;IT principles&quot;</description>
 <language>en</language>
<item>
 <title>Provide Expert Judgement</title>
 <link>http://www.itskeptic.org/content/it-principles#comment-9486</link>
 <description>&lt;p&gt;I think one more overarching principle is to provide expert judgement related to technology and industry evolution. (relevant to your organization)&lt;/p&gt;
&lt;p&gt;Senior IT Managers need to clearly express when technical solutions will support the business or are no longer fit for purpose.&lt;/p&gt;
&lt;p&gt;The concept of expertise in our vertical is one we ofter overlook as a service we provide. To be a trusted partner within the business you need to be able to  communicate what is possible and what is not, in clear &quot;jargon free&quot; language.&lt;/p&gt;
&lt;p&gt;Maybe the principle is to use expert judgement to interpret business requirements, identify risks, assist with defining the level of acceptable risk from an IS/IT point of view; and develop solutions that fit this risk appetite.&lt;/p&gt;
</description>
 <pubDate>Thu, 12 Jul 2012 14:01:05 +0000</pubDate>
 <dc:creator>Glen</dc:creator>
 <guid isPermaLink="false">comment 9486 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Nice, thanks Glen
To which</title>
 <link>http://www.itskeptic.org/content/it-principles#comment-9483</link>
 <description>&lt;p&gt;Nice, thanks Glen&lt;br /&gt;
To which I&#039;d add: to protect and serve, a balance of risk and value.&lt;/p&gt;
</description>
 <pubDate>Wed, 11 Jul 2012 21:35:54 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">comment 9483 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Design, Build, Operate</title>
 <link>http://www.itskeptic.org/content/it-principles#comment-9481</link>
 <description>&lt;p&gt;IT Seeks to:&lt;/p&gt;
&lt;p&gt;Design solutions in support of expressed business needs;&lt;br /&gt;
Build these solutions in alignment with the availabilty, capacity and functionality needs of the business;&lt;br /&gt;
Operate solutions in an effective and efficient manner, maintaining the required access and uptimes.&lt;/p&gt;
&lt;p&gt;It Provides:&lt;br /&gt;
A secure, robust IT infrastructure;&lt;br /&gt;
Subject Matter expertise to interpret business needs and analyze the existing and emerging technology platforms to provide cost effective solutions;&lt;br /&gt;
Provide services in alignment to the ongoing needs and requirements of the business;&lt;/p&gt;
</description>
 <pubDate>Wed, 11 Jul 2012 20:15:24 +0000</pubDate>
 <dc:creator>Glen</dc:creator>
 <guid isPermaLink="false">comment 9481 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>10 more IT principles</title>
 <link>http://www.itskeptic.org/content/it-principles#comment-9464</link>
 <description>&lt;p&gt;
James Robertson at StepTwo Designs &lt;a href=&quot;http://www.steptwo.com.au/papers/kmc_effectiveim/index.html&quot; target=&quot;_blank&quot;&gt;  lists these 10 (see the article for full discussion of them)&lt;/a&gt; &lt;/p&gt;
&lt;p&gt;recognise (and manage) complexity&lt;br /&gt;
focus on adoption&lt;br /&gt;
deliver tangible &amp;amp; visible benefits&lt;br /&gt;
prioritise according to business needs&lt;br /&gt;
take a journey of a thousand steps&lt;br /&gt;
provide strong leadership&lt;br /&gt;
mitigate risks&lt;br /&gt;
communicate extensively&lt;br /&gt;
aim to deliver a seamless user experience&lt;br /&gt;
choose the first project very carefully&lt;/p&gt;
&lt;p&gt;Thanks to &lt;a href=&quot;http://twitter.com/BGInfoSecKnight&quot; target=&quot;_blank&quot;&gt; @BGInfoSecKnight&lt;/a&gt; &lt;/p&gt;
</description>
 <pubDate>Wed, 04 Jul 2012 22:23:01 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">comment 9464 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Transparency</title>
 <link>http://www.itskeptic.org/content/it-principles#comment-9455</link>
 <description>&lt;p&gt;IT will produce reporting for key stakeholders in order to enable good decision making regarding governance and management of IT.&lt;/p&gt;
&lt;p&gt;While this may be a subset of the external vs internal view of IT, it still needs to be called out.&lt;/p&gt;
</description>
 <pubDate>Thu, 28 Jun 2012 22:20:01 +0000</pubDate>
 <dc:creator>RogertheITSMGuy</dc:creator>
 <guid isPermaLink="false">comment 9455 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>Keep it simple</title>
 <link>http://www.itskeptic.org/content/it-principles#comment-9451</link>
 <description>&lt;p&gt;Keep it simple.&lt;/p&gt;
</description>
 <pubDate>Wed, 27 Jun 2012 15:46:15 +0000</pubDate>
 <dc:creator>Osama S.</dc:creator>
 <guid isPermaLink="false">comment 9451 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>this is a great set of</title>
 <link>http://www.itskeptic.org/content/it-principles#comment-9450</link>
 <description>&lt;p&gt;this is a great set of principles &lt;a href=&quot;http://www.unimelb.edu.au/infostrategy/policies/it_principles.html&quot; title=&quot;http://www.unimelb.edu.au/infostrategy/policies/it_principles.html&quot;&gt;http://www.unimelb.edu.au/infostrategy/policies/it_principles.html&lt;/a&gt; thank-you @BGInfoSecKnight&lt;/p&gt;
</description>
 <pubDate>Wed, 27 Jun 2012 15:43:20 +0000</pubDate>
 <dc:creator>skeptic</dc:creator>
 <guid isPermaLink="false">comment 9450 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>IT Principles</title>
 <link>http://www.itskeptic.org/content/it-principles#comment-9449</link>
 <description>&lt;p&gt;Governance criteria for Technology: Technology made available to the business to exploit efficiencies &amp;amp; connectivity balanced against the realities such as ease of use and reliability (e.g. utility &amp;amp; warranty) (The ITDYNMICStm governance framework)&lt;/p&gt;
</description>
 <pubDate>Wed, 27 Jun 2012 12:32:26 +0000</pubDate>
 <dc:creator>Jaqi Haworth</dc:creator>
 <guid isPermaLink="false">comment 9449 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>IT Principles</title>
 <link>http://www.itskeptic.org/content/it-principles#comment-9448</link>
 <description>&lt;p&gt;Mapping the 6 layers (ownership, business processes, applications, systems, hardware and infrastructure) and corresponding elements (people, process and technology) is an important framework for understanding how the business works, and determine the IT assets &amp;amp; enablers that make the business work (OBASHI)&lt;/p&gt;
</description>
 <pubDate>Wed, 27 Jun 2012 12:21:15 +0000</pubDate>
 <dc:creator>Jaqi Haworth</dc:creator>
 <guid isPermaLink="false">comment 9448 at http://www.itskeptic.org</guid>
</item>
<item>
 <title>How about: &quot;IT will seek</title>
 <link>http://www.itskeptic.org/content/it-principles#comment-9447</link>
 <description>&lt;p&gt;How about: &quot;IT will seek customer participation/input whenever feasible/possible&quot;. I&#039;ve seen it happen a lot where, for example, there is no customer participation in the CAB, or during the Service Design process.&lt;/p&gt;
&lt;p&gt;My 2.&lt;/p&gt;
&lt;p&gt;J.,&lt;/p&gt;
</description>
 <pubDate>Wed, 27 Jun 2012 11:40:05 +0000</pubDate>
 <dc:creator>Visitor</dc:creator>
 <guid isPermaLink="false">comment 9447 at http://www.itskeptic.org</guid>
</item>
</channel>
</rss>
