<?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 on: How to Ruin an IT Project</title>
	<atom:link href="http://aboveandbeyondkm.com/2009/06/how-to-ruin-an-it-project.html/feed" rel="self" type="application/rss+xml" />
	<link>http://aboveandbeyondkm.com/2009/06/how-to-ruin-an-it-project.html</link>
	<description>A discussion of knowledge management that goes above and beyond technology.</description>
	<lastBuildDate>Sat, 24 Jul 2010 00:55:00 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: VMaryAbraham</title>
		<link>http://aboveandbeyondkm.com/2009/06/how-to-ruin-an-it-project.html/comment-page-1#comment-1501</link>
		<dc:creator>VMaryAbraham</dc:creator>
		<pubDate>Wed, 01 Jul 2009 08:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://aboveandbeyondkm.com/?p=1071#comment-1501</guid>
		<description>Paula -&lt;br&gt;&lt;br&gt;You definitely were ahead of the rest of us in the 1990s.  Given the inherent shortcomings of requirements, why do IT departments around the world still cling to them?  Inertia?  Willful blindness? &lt;br&gt;&lt;br&gt;- Mary</description>
		<content:encoded><![CDATA[<p>Paula -</p>
<p>You definitely were ahead of the rest of us in the 1990s.  Given the inherent shortcomings of requirements, why do IT departments around the world still cling to them?  Inertia?  Willful blindness? </p>
<p>- Mary</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMaryAbraham</title>
		<link>http://aboveandbeyondkm.com/2009/06/how-to-ruin-an-it-project.html/comment-page-1#comment-1502</link>
		<dc:creator>VMaryAbraham</dc:creator>
		<pubDate>Wed, 01 Jul 2009 08:31:08 +0000</pubDate>
		<guid isPermaLink="false">http://aboveandbeyondkm.com/?p=1071#comment-1502</guid>
		<description>Thanks, Sean.  I&#039;d love to know what your PM folks thought of it!&lt;br&gt;&lt;br&gt;- Mary</description>
		<content:encoded><![CDATA[<p>Thanks, Sean.  I&#39;d love to know what your PM folks thought of it!</p>
<p>- Mary</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rotkapchen</title>
		<link>http://aboveandbeyondkm.com/2009/06/how-to-ruin-an-it-project.html/comment-page-1#comment-1500</link>
		<dc:creator>rotkapchen</dc:creator>
		<pubDate>Wed, 01 Jul 2009 06:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://aboveandbeyondkm.com/?p=1071#comment-1500</guid>
		<description>In the mid-90s I had a presentation &quot;Requirements Don&#039;t Work&quot; that began to circle in on some of the same topics I&#039;m spewing today. The relevant evidences have just increased in detail.&lt;br&gt;&lt;br&gt;So far the best placeholder is to leverage Design Thinking fundamentals. While there are a variety of ways to consider the approaches, this article details the fundamentals most relevant to IT &lt;a href=&quot;http://twurl.nl/5t3dlc&quot; rel=&quot;nofollow&quot;&gt;http://twurl.nl/5t3dlc&lt;/a&gt;&lt;br&gt;&lt;br&gt;My own summary of relevance:&lt;br&gt;Immersive Research -- establish the relevant context&lt;br&gt;Collaborative Discovery -- even with paper artifacts a process of &#039;winnowing&#039; possibilities allows for &#039;failing faster&#039; (This? No, This? This and This?)&lt;br&gt;Collaborative Development -- Moving into construction with same methods as last phase&lt;br&gt;Continuous Adaptation -- via feedback loops (business conditions constantly change -- there is no Done)</description>
		<content:encoded><![CDATA[<p>In the mid-90s I had a presentation &#8220;Requirements Don&#39;t Work&#8221; that began to circle in on some of the same topics I&#39;m spewing today. The relevant evidences have just increased in detail.</p>
<p>So far the best placeholder is to leverage Design Thinking fundamentals. While there are a variety of ways to consider the approaches, this article details the fundamentals most relevant to IT <a href="http://twurl.nl/5t3dlc" rel="nofollow">http://twurl.nl/5t3dlc</a></p>
<p>My own summary of relevance:<br />Immersive Research &#8212; establish the relevant context<br />Collaborative Discovery &#8212; even with paper artifacts a process of &#39;winnowing&#39; possibilities allows for &#39;failing faster&#39; (This? No, This? This and This?)<br />Collaborative Development &#8212; Moving into construction with same methods as last phase<br />Continuous Adaptation &#8212; via feedback loops (business conditions constantly change &#8212; there is no Done)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMaryAbraham</title>
		<link>http://aboveandbeyondkm.com/2009/06/how-to-ruin-an-it-project.html/comment-page-1#comment-799</link>
		<dc:creator>VMaryAbraham</dc:creator>
		<pubDate>Wed, 01 Jul 2009 04:35:17 +0000</pubDate>
		<guid isPermaLink="false">http://aboveandbeyondkm.com/?p=1071#comment-799</guid>
		<description>Paula -&lt;br&gt;&lt;br&gt;You definitely were ahead of the rest of us in the 1990s.  Given the inherent shortcomings of requirements, why do IT departments around the world still cling to them?  Inertia?  Willful blindness? &lt;br&gt;&lt;br&gt;- Mary</description>
		<content:encoded><![CDATA[<p>Paula -</p>
<p>You definitely were ahead of the rest of us in the 1990s.  Given the inherent shortcomings of requirements, why do IT departments around the world still cling to them?  Inertia?  Willful blindness? </p>
<p>- Mary</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: VMaryAbraham</title>
		<link>http://aboveandbeyondkm.com/2009/06/how-to-ruin-an-it-project.html/comment-page-1#comment-798</link>
		<dc:creator>VMaryAbraham</dc:creator>
		<pubDate>Wed, 01 Jul 2009 04:31:08 +0000</pubDate>
		<guid isPermaLink="false">http://aboveandbeyondkm.com/?p=1071#comment-798</guid>
		<description>Thanks, Sean.  I&#039;d love to know what your PM folks thought of it!&lt;br&gt;&lt;br&gt;- Mary</description>
		<content:encoded><![CDATA[<p>Thanks, Sean.  I&#39;d love to know what your PM folks thought of it!</p>
<p>- Mary</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rotkapchen</title>
		<link>http://aboveandbeyondkm.com/2009/06/how-to-ruin-an-it-project.html/comment-page-1#comment-797</link>
		<dc:creator>rotkapchen</dc:creator>
		<pubDate>Wed, 01 Jul 2009 02:21:38 +0000</pubDate>
		<guid isPermaLink="false">http://aboveandbeyondkm.com/?p=1071#comment-797</guid>
		<description>In the mid-90s I had a presentation &quot;Requirements Don&#039;t Work&quot; that began to circle in on some of the same topics I&#039;m spewing today. The relevant evidences have just increased in detail.&lt;br&gt;&lt;br&gt;So far the best placeholder is to leverage Design Thinking fundamentals. While there are a variety of ways to consider the approaches, this article details the fundamentals most relevant to IT &lt;a href=&quot;http://twurl.nl/5t3dlc&quot; rel=&quot;nofollow&quot;&gt;http://twurl.nl/5t3dlc&lt;/a&gt;&lt;br&gt;&lt;br&gt;My own summary of relevance:&lt;br&gt;Immersive Research -- establish the relevant context&lt;br&gt;Collaborative Discovery -- even with paper artifacts a process of &#039;winnowing&#039; possibilities allows for &#039;failing faster&#039; (This? No, This? This and This?)&lt;br&gt;Collaborative Development -- Moving into construction with same methods as last phase&lt;br&gt;Continuous Adaptation -- via feedback loops (business conditions constantly change -- there is no Done)</description>
		<content:encoded><![CDATA[<p>In the mid-90s I had a presentation &#8220;Requirements Don&#39;t Work&#8221; that began to circle in on some of the same topics I&#39;m spewing today. The relevant evidences have just increased in detail.</p>
<p>So far the best placeholder is to leverage Design Thinking fundamentals. While there are a variety of ways to consider the approaches, this article details the fundamentals most relevant to IT <a href="http://twurl.nl/5t3dlc" rel="nofollow">http://twurl.nl/5t3dlc</a></p>
<p>My own summary of relevance:<br />Immersive Research &#8212; establish the relevant context<br />Collaborative Discovery &#8212; even with paper artifacts a process of &#39;winnowing&#39; possibilities allows for &#39;failing faster&#39; (This? No, This? This and This?)<br />Collaborative Development &#8212; Moving into construction with same methods as last phase<br />Continuous Adaptation &#8212; via feedback loops (business conditions constantly change &#8212; there is no Done)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: seanabrady</title>
		<link>http://aboveandbeyondkm.com/2009/06/how-to-ruin-an-it-project.html/comment-page-1#comment-795</link>
		<dc:creator>seanabrady</dc:creator>
		<pubDate>Tue, 30 Jun 2009 15:15:27 +0000</pubDate>
		<guid isPermaLink="false">http://aboveandbeyondkm.com/?p=1071#comment-795</guid>
		<description>That is a great image.  It sums things up very, very well.  Forwarded on to our PM folks.</description>
		<content:encoded><![CDATA[<p>That is a great image.  It sums things up very, very well.  Forwarded on to our PM folks.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
