<?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: Defining the Last Responsible Moment</title>
	<atom:link href="http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/feed/" rel="self" type="application/rss+xml" />
	<link>http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=defining-the-last-responsible-moment</link>
	<description>Karl Scotland - Using Agile to Deliver Value</description>
	<lastBuildDate>Mon, 14 May 2012 03:22:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Agile, Team Work, Leadership &#187; Blog Archive &#187; Why the LRM is just theory?</title>
		<link>http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/comment-page-1/#comment-84346</link>
		<dc:creator>Agile, Team Work, Leadership &#187; Blog Archive &#187; Why the LRM is just theory?</dc:creator>
		<pubDate>Thu, 15 Dec 2011 21:30:16 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=574#comment-84346</guid>
		<description>[...] about the usefulness of the Last Responsible Moment (LRM) in the context of a complex project. The LRM is when the Cost of Delay overweights the Benefits of Delay. In other words, it&#8217;s often [...]</description>
		<content:encoded><![CDATA[<p>[...] about the usefulness of the Last Responsible Moment (LRM) in the context of a complex project. The LRM is when the Cost of Delay overweights the Benefits of Delay. In other words, it&#8217;s often [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Last Responsible Moment—A Mindset &#124; Lean Procrastination</title>
		<link>http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/comment-page-1/#comment-72523</link>
		<dc:creator>Last Responsible Moment—A Mindset &#124; Lean Procrastination</dc:creator>
		<pubDate>Mon, 10 Oct 2011 06:57:06 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=574#comment-72523</guid>
		<description>[...] of delay just outweighs the benefit of delay (though I value this economic thinking suggested by Karl Scotland). To me, last is a constant reminder that I might not yet have evaluated all options of [...]</description>
		<content:encoded><![CDATA[<p>[...] of delay just outweighs the benefit of delay (though I value this economic thinking suggested by Karl Scotland). To me, last is a constant reminder that I might not yet have evaluated all options of [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Why I Don&#8217;t Attend Agile2011&#8230; &#171; OlafLewitz</title>
		<link>http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/comment-page-1/#comment-52393</link>
		<dc:creator>Why I Don&#8217;t Attend Agile2011&#8230; &#171; OlafLewitz</dc:creator>
		<pubDate>Wed, 10 Aug 2011 08:44:44 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=574#comment-52393</guid>
		<description>[...] with the example, “when to submit to Agile2011?” (Karl Scotland elaborated on that topic here.) After short discussions with the people I intended to do my submissions for XP2011 together [...]</description>
		<content:encoded><![CDATA[<p>[...] with the example, “when to submit to Agile2011?” (Karl Scotland elaborated on that topic here.) After short discussions with the people I intended to do my submissions for XP2011 together [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Quick Agile Links #12 &#8211; nemrac.com</title>
		<link>http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/comment-page-1/#comment-7583</link>
		<dc:creator>Quick Agile Links #12 &#8211; nemrac.com</dc:creator>
		<pubDate>Thu, 29 Apr 2010 01:49:35 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=574#comment-7583</guid>
		<description>[...] flexibility down the road. Now Karl Scotland has written an elegant post that shows the what the Last Responsible Moment(s) are for Agile2010 conference [...]</description>
		<content:encoded><![CDATA[<p>[...] flexibility down the road. Now Karl Scotland has written an elegant post that shows the what the Last Responsible Moment(s) are for Agile2010 conference [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: allan kelly</title>
		<link>http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/comment-page-1/#comment-6446</link>
		<dc:creator>allan kelly</dc:creator>
		<pubDate>Thu, 08 Apr 2010 08:27:38 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=574#comment-6446</guid>
		<description>Nice abstraction, there are a lot of context specific modifiers I would want to include.

Take a conference I know well, I used to be on the organizing committee: I can extend my own deadline by submitting a place holder before the deadline knowing that I know the committee well enough that they will check back with me during the review process
That doesn&#039;t scale, if everyone does it the system breaks down.  When I&#039;m on the committee I hate people doing that becuase it makes my job more difficult (expensive).

Put it another way, I (submitter) can increase the value (to me) by extending my deadline, but I increase the cost to the organizers.  Is there any value add?  Or just value transfer?

Another conference I know: my submission experience suggests the organizers value JIT submissions highly and early submissions at zero.  They have an open review process and when I submit early nobody looks at the proposal.  Submit late, when everyone else is submitting (and reviewing) and it gets attention.

Bringing this back to LRM...

Its a bit like physics &quot;friction free surface&quot;, sooner or later you need to account for context, and as usual, the hard bit (the Devil or God, take your pick) is in the detail</description>
		<content:encoded><![CDATA[<p>Nice abstraction, there are a lot of context specific modifiers I would want to include.</p>
<p>Take a conference I know well, I used to be on the organizing committee: I can extend my own deadline by submitting a place holder before the deadline knowing that I know the committee well enough that they will check back with me during the review process<br />
That doesn&#8217;t scale, if everyone does it the system breaks down.  When I&#8217;m on the committee I hate people doing that becuase it makes my job more difficult (expensive).</p>
<p>Put it another way, I (submitter) can increase the value (to me) by extending my deadline, but I increase the cost to the organizers.  Is there any value add?  Or just value transfer?</p>
<p>Another conference I know: my submission experience suggests the organizers value JIT submissions highly and early submissions at zero.  They have an open review process and when I submit early nobody looks at the proposal.  Submit late, when everyone else is submitting (and reviewing) and it gets attention.</p>
<p>Bringing this back to LRM&#8230;</p>
<p>Its a bit like physics &#8220;friction free surface&#8221;, sooner or later you need to account for context, and as usual, the hard bit (the Devil or God, take your pick) is in the detail</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/comment-page-1/#comment-6394</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Wed, 07 Apr 2010 08:50:44 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=574#comment-6394</guid>
		<description>Thanks Brian. There&#039;s a difference between Benefit of Delay, and Benefit of Attending. I could be clearer on that difference and I think the final example needs some more work.

I&#039;m not too worried about trying to quantify the costs and benefits precisely. Its more about the conversation and resulting shared mental model provided by the shapes of the graphs.</description>
		<content:encoded><![CDATA[<p>Thanks Brian. There&#8217;s a difference between Benefit of Delay, and Benefit of Attending. I could be clearer on that difference and I think the final example needs some more work.</p>
<p>I&#8217;m not too worried about trying to quantify the costs and benefits precisely. Its more about the conversation and resulting shared mental model provided by the shapes of the graphs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/comment-page-1/#comment-6393</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Wed, 07 Apr 2010 08:40:08 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=574#comment-6393</guid>
		<description>Ah. Yes, I see that the Cost of Delay is reduced much more due to sunk cost. Thanks. I still think that there is Benefit of Delay. Why submit early when you don&#039;t have to submit at all?

I can&#039;t actually make LWS this week. Shame you can&#039;t make LSSC10. Next time though!</description>
		<content:encoded><![CDATA[<p>Ah. Yes, I see that the Cost of Delay is reduced much more due to sunk cost. Thanks. I still think that there is Benefit of Delay. Why submit early when you don&#8217;t have to submit at all?</p>
<p>I can&#8217;t actually make LWS this week. Shame you can&#8217;t make LSSC10. Next time though!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Brian Marick</title>
		<link>http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/comment-page-1/#comment-6387</link>
		<dc:creator>Brian Marick</dc:creator>
		<pubDate>Tue, 06 Apr 2010 22:15:41 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=574#comment-6387</guid>
		<description>This is nice, really nice. Still, there&#039;s a little bit of unit mixing in your description. I notice that in the beginning, your description of Benefit uses these words: &quot;speaker benefits including conference registration, complimentary hotel nights.&quot; Later, you use a considerably less specific &quot;so important and valuable to say&quot; to talk about the Benefits of acting late.

That&#039;s one of the things I worry about when it comes to such cost/benefit analyses. That which is easily quantifiable (cost of hotel rooms) comes to dominate the qualitative (what you get out of speaking). In unsubtle hands, the qualitative gets completely ignored, leading to bad decisions.

What happens if different benefits and different costs are incommensurable, if not everything can be converted into, say, euros?</description>
		<content:encoded><![CDATA[<p>This is nice, really nice. Still, there&#8217;s a little bit of unit mixing in your description. I notice that in the beginning, your description of Benefit uses these words: &#8220;speaker benefits including conference registration, complimentary hotel nights.&#8221; Later, you use a considerably less specific &#8220;so important and valuable to say&#8221; to talk about the Benefits of acting late.</p>
<p>That&#8217;s one of the things I worry about when it comes to such cost/benefit analyses. That which is easily quantifiable (cost of hotel rooms) comes to dominate the qualitative (what you get out of speaking). In unsubtle hands, the qualitative gets completely ignored, leading to bad decisions.</p>
<p>What happens if different benefits and different costs are incommensurable, if not everything can be converted into, say, euros?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Dolman-Darrall</title>
		<link>http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/comment-page-1/#comment-6384</link>
		<dc:creator>Paul Dolman-Darrall</dc:creator>
		<pubDate>Tue, 06 Apr 2010 20:21:05 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=574#comment-6384</guid>
		<description>One for the pub on Thursday. However once the ticket has been purchased it should no longer be included in the decision.

Thus the cost of delay is losing the opportunity to have the work iterated, feedback and get a guaranteed spot, the ticket price is no longer a factor.

The benefit of delay is nothing, there is no benefit in delaying. He has already purchased the ticket.

The simplicity is good, but it leads the wrong choice in the final answer.</description>
		<content:encoded><![CDATA[<p>One for the pub on Thursday. However once the ticket has been purchased it should no longer be included in the decision.</p>
<p>Thus the cost of delay is losing the opportunity to have the work iterated, feedback and get a guaranteed spot, the ticket price is no longer a factor.</p>
<p>The benefit of delay is nothing, there is no benefit in delaying. He has already purchased the ticket.</p>
<p>The simplicity is good, but it leads the wrong choice in the final answer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Karl</title>
		<link>http://availagility.co.uk/2010/04/06/defining-the-last-responsible-moment/comment-page-1/#comment-6383</link>
		<dc:creator>Karl</dc:creator>
		<pubDate>Tue, 06 Apr 2010 20:15:07 +0000</pubDate>
		<guid isPermaLink="false">http://availagility.co.uk/?p=574#comment-6383</guid>
		<description>Hi Paul,

Not sure I understand your argument. I wasn&#039;t consciously allowing sunk cost, although I was ignoring the &quot;option cost&quot; for simplicity. 

Karl</description>
		<content:encoded><![CDATA[<p>Hi Paul,</p>
<p>Not sure I understand your argument. I wasn&#8217;t consciously allowing sunk cost, although I was ignoring the &#8220;option cost&#8221; for simplicity. </p>
<p>Karl</p>
]]></content:encoded>
	</item>
</channel>
</rss>

