<?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: On Agile, IT-Business Alignment, Martin Fowler and The Yawning Crevasse of Doom</title>
	<atom:link href="http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/</link>
	<description>An industry analyst blog looking at software ecosystems and convergence</description>
	<lastBuildDate>Sun, 21 Mar 2010 03:26:39 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Kelly Waters</title>
		<link>http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/comment-page-1/#comment-63459</link>
		<dc:creator>Kelly Waters</dc:creator>
		<pubDate>Wed, 18 Apr 2007 21:38:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/#comment-63459</guid>
		<description>You or your readers may be interested in this blog all about agile development:

http://www.allaboutagile.com 

In particular there is a description of 10 key principles of agile development irrespective of which methodology you may be using: 

http://kw-agiledevelopment.blogspot.com/2007/02/10-things-you-need-to-know-about-agile.html

And there&#039;s also an agile development forum &quot;all about agile&quot; for further discussion with peers:

http://www.groups.google.com/group/allaboutagile

I hope these resources are useful.

Kelly Waters
http://www.allaboutagile.com</description>
		<content:encoded><![CDATA[<p>You or your readers may be interested in this blog all about agile development:</p>
<p><a href="http://www.allaboutagile.com" rel="nofollow">http://www.allaboutagile.com</a> </p>
<p>In particular there is a description of 10 key principles of agile development irrespective of which methodology you may be using: </p>
<p><a href="http://kw-agiledevelopment.blogspot.com/2007/02/10-things-you-need-to-know-about-agile.html" rel="nofollow">http://kw-agiledevelopment.blogspot.com/2007/02/10-things-you-need-to-know-about-agile.html</a></p>
<p>And there&#8217;s also an agile development forum &#8220;all about agile&#8221; for further discussion with peers:</p>
<p><a href="http://www.groups.google.com/group/allaboutagile" rel="nofollow">http://www.groups.google.com/group/allaboutagile</a></p>
<p>I hope these resources are useful.</p>
<p>Kelly Waters<br />
<a href="http://www.allaboutagile.com" rel="nofollow">http://www.allaboutagile.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed_Dodds</title>
		<link>http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/comment-page-1/#comment-56647</link>
		<dc:creator>Ed_Dodds</dc:creator>
		<pubDate>Mon, 09 Apr 2007 18:04:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/#comment-56647</guid>
		<description>Ok, Grassley is looking - http://www.desmoinesregister.com/apps/pbcs.dll/article?AID=2007704060380</description>
		<content:encoded><![CDATA[<p>Ok, Grassley is looking &#8211; <a href="http://www.desmoinesregister.com/apps/pbcs.dll/article?AID=2007704060380" rel="nofollow">http://www.desmoinesregister.com/apps/pbcs.dll/article?AID=2007704060380</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ed Dodds</title>
		<link>http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/comment-page-1/#comment-56126</link>
		<dc:creator>Ed Dodds</dc:creator>
		<pubDate>Sun, 08 Apr 2007 12:11:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/#comment-56126</guid>
		<description>In a word: fraud ( or corruption ). Anyone who tracks current management strategy books knows that the trend du jour is on the emphasis in on opening the budgets, pushing the decision making down to the front line users, letting them set the case for funding -- but that&#039;s NOT what is done. Why? Well, the auditor ( or xbrl ). What if your industry is built on bribes, kickbacks, corruption in general. What if everyone in industry knows it -- but noone says it outloud. Ever try to build a UML diagram with a placeholder for graft? To oversimplify, there are only three impediments to a more mature geek-biz user parnership: 1) C-Suite full of greed-head immorals worried about short-term stock price driven targets -- long-term business viability be damned; 2) there is no standard business process; 3) the standard business process involve illegalities. Why do you think so many US businesses are choosing to go private at just the moment SOX is being understood well enough to actually be effective. Why is it the US biz news and politicians say &quot;healthcare is too expensive&quot; but never follow it up with &quot;well, I wonder where the money is actually going now?&quot;</description>
		<content:encoded><![CDATA[<p>In a word: fraud ( or corruption ). Anyone who tracks current management strategy books knows that the trend du jour is on the emphasis in on opening the budgets, pushing the decision making down to the front line users, letting them set the case for funding &#8212; but that&#8217;s NOT what is done. Why? Well, the auditor ( or xbrl ). What if your industry is built on bribes, kickbacks, corruption in general. What if everyone in industry knows it &#8212; but noone says it outloud. Ever try to build a UML diagram with a placeholder for graft? To oversimplify, there are only three impediments to a more mature geek-biz user parnership: 1) C-Suite full of greed-head immorals worried about short-term stock price driven targets &#8212; long-term business viability be damned; 2) there is no standard business process; 3) the standard business process involve illegalities. Why do you think so many US businesses are choosing to go private at just the moment SOX is being understood well enough to actually be effective. Why is it the US biz news and politicians say &#8220;healthcare is too expensive&#8221; but never follow it up with &#8220;well, I wonder where the money is actually going now?&#8221;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ric</title>
		<link>http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/comment-page-1/#comment-55202</link>
		<dc:creator>Ric</dc:creator>
		<pubDate>Sat, 07 Apr 2007 14:58:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/#comment-55202</guid>
		<description>“Any profession has jargon” - I had a quite discussion one day with a winemaker and a viticulturist - they both out-acronymed me easily ...

I agree with Bill about the contractual difficulties - waterfall survives because it covers more arses - Agile exposes too many dickheads for the corporate machine to be comfortable with it.</description>
		<content:encoded><![CDATA[<p>“Any profession has jargon” &#8211; I had a quite discussion one day with a winemaker and a viticulturist &#8211; they both out-acronymed me easily &#8230;</p>
<p>I agree with Bill about the contractual difficulties &#8211; waterfall survives because it covers more arses &#8211; Agile exposes too many dickheads for the corporate machine to be comfortable with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Enterprise Decision Management - a Weblog</title>
		<link>http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/comment-page-1/#comment-54203</link>
		<dc:creator>Enterprise Decision Management - a Weblog</dc:creator>
		<pubDate>Fri, 06 Apr 2007 16:04:21 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/#comment-54203</guid>
		<description>&lt;strong&gt;Are business rules a bridge or a ferry?...&lt;/strong&gt;

James Governer had a great post today - On Agile, IT-Business Alignment, Martin Fowler and The Yawning Crevasse of Doom talking about a presentation by Martin Fowler and Dan North. There were some wonderful comments in it: The biggest problem...</description>
		<content:encoded><![CDATA[<p><strong>Are business rules a bridge or a ferry?&#8230;</strong></p>
<p>James Governer had a great post today &#8211; On Agile, IT-Business Alignment, Martin Fowler and The Yawning Crevasse of Doom talking about a presentation by Martin Fowler and Dan North. There were some wonderful comments in it: The biggest problem&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: James Taylor</title>
		<link>http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/comment-page-1/#comment-54184</link>
		<dc:creator>James Taylor</dc:creator>
		<pubDate>Fri, 06 Apr 2007 15:47:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/#comment-54184</guid>
		<description>Great post - I love the bridge / ferry analogy!
I think that if you want to &quot;Create a ubiquitous language, where he names of the classes and how they are combined matches the business conversation&quot; then you can just use a business rules management system. They work, they let you write business-friendly logic and they mostly support ways to build templates that let business users manage some of their rules. This helps close the gap between the different perspectives of IT and the business (about which I have blogged - http://www.edmblog.com/weblog/2005/08/different_persp.html) and solve one of the major problems with (for?) programmers (http://www.edmblog.com/weblog/2006/11/the_problem_wit.html).
JT
http://www.edmblog.com</description>
		<content:encoded><![CDATA[<p>Great post &#8211; I love the bridge / ferry analogy!<br />
I think that if you want to &#8220;Create a ubiquitous language, where he names of the classes and how they are combined matches the business conversation&#8221; then you can just use a business rules management system. They work, they let you write business-friendly logic and they mostly support ways to build templates that let business users manage some of their rules. This helps close the gap between the different perspectives of IT and the business (about which I have blogged &#8211; <a href="http://www.edmblog.com/weblog/2005/08/different_persp.html)" rel="nofollow">http://www.edmblog.com/weblog/2005/08/different_persp.html)</a> and solve one of the major problems with (for?) programmers (<a href="http://www.edmblog.com/weblog/2006/11/the_problem_wit.html" rel="nofollow">http://www.edmblog.com/weblog/2006/11/the_problem_wit.html</a>).<br />
JT<br />
<a href="http://www.edmblog.com" rel="nofollow">http://www.edmblog.com</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bill de hOra</title>
		<link>http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/comment-page-1/#comment-53484</link>
		<dc:creator>Bill de hOra</dc:creator>
		<pubDate>Thu, 05 Apr 2007 23:49:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.redmonk.com/jgovernor/2007/04/05/on-agile-it-business-alignment-martin-fowler-and-the-yawning-crevasse-of-doom/#comment-53484</guid>
		<description>“We know better than you, so we’ll overwhelm you with technical details.”

Not sure about that. Let me tell you why.

&quot;One way to overcome this barrier is to make design decisions later in the process - rather than thinking through every potential scenario and developing accordingly, only set things in stone once they are needed. “We don&#039;t need to make the decision now. make it when we need to. Its easier.”&quot;

I keep saying this, but the idea of deferred decision making does not fly under orthodox commercial arrangements, especially fixed price. FP demands decisions are made up front and the customer scope is tightly controlled. I don&#039;t agree it&#039;s a good model, but the two extremes, agile and bduf exhortations do not produce results under FP. It&#039;s a pity someone wasn&#039;t there to ask Fowler about this, because he damn well knows agile and FP don&#039;t mesh.

The biggest problems in IT delivery are contractual, not communicative. If you want agile development you need agile contracts (ask Cote&#039; if you don&#039;t believe me). The models that seem to work are VC style rounded funding - more project money is realised on results - yet most governance/compliance process mitigates against that work style. There&#039;s all this this talk about aligning IT with business as if IT held the burden of responsibility and didn&#039;t get business, but seriously how many business stakeholders get delivery dynamics? I say the technical tribes have a far greater understanding of project dynamics whereas much business decision making and contracts are utterly naive and optimized for project failure. As a technical person, it&#039;s very very frustrating to be set up to fail; it&#039;s even more frustrating to see an utter lack of understanding as to how contract structures drive projects. It&#039;s problem number one. Why is no-one talking about this?</description>
		<content:encoded><![CDATA[<p>“We know better than you, so we’ll overwhelm you with technical details.”</p>
<p>Not sure about that. Let me tell you why.</p>
<p>&#8220;One way to overcome this barrier is to make design decisions later in the process &#8211; rather than thinking through every potential scenario and developing accordingly, only set things in stone once they are needed. “We don&#8217;t need to make the decision now. make it when we need to. Its easier.”&#8221;</p>
<p>I keep saying this, but the idea of deferred decision making does not fly under orthodox commercial arrangements, especially fixed price. FP demands decisions are made up front and the customer scope is tightly controlled. I don&#8217;t agree it&#8217;s a good model, but the two extremes, agile and bduf exhortations do not produce results under FP. It&#8217;s a pity someone wasn&#8217;t there to ask Fowler about this, because he damn well knows agile and FP don&#8217;t mesh.</p>
<p>The biggest problems in IT delivery are contractual, not communicative. If you want agile development you need agile contracts (ask Cote&#8217; if you don&#8217;t believe me). The models that seem to work are VC style rounded funding &#8211; more project money is realised on results &#8211; yet most governance/compliance process mitigates against that work style. There&#8217;s all this this talk about aligning IT with business as if IT held the burden of responsibility and didn&#8217;t get business, but seriously how many business stakeholders get delivery dynamics? I say the technical tribes have a far greater understanding of project dynamics whereas much business decision making and contracts are utterly naive and optimized for project failure. As a technical person, it&#8217;s very very frustrating to be set up to fail; it&#8217;s even more frustrating to see an utter lack of understanding as to how contract structures drive projects. It&#8217;s problem number one. Why is no-one talking about this?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
