<?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: Representation of structure</title>
	<atom:link href="http://leansoftwareengineering.com/2009/02/09/representation-of-structure/feed/" rel="self" type="application/rss+xml" />
	<link>http://leansoftwareengineering.com/2009/02/09/representation-of-structure/</link>
	<description>Essays on the Continuous Delivery of High Quality Information Systems</description>
	<lastBuildDate>Wed, 01 Feb 2012 18:32:04 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Neeraj Sangal</title>
		<link>http://leansoftwareengineering.com/2009/02/09/representation-of-structure/comment-page-1/#comment-4977</link>
		<dc:creator>Neeraj Sangal</dc:creator>
		<pubDate>Fri, 06 Mar 2009 13:26:08 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/?p=994#comment-4977</guid>
		<description>Looking forward to future postings from you regarding maintenance of system structure using DSMs. Here is a paper which show how DSMs can be used to represent and maintain the architecture of large scale software: http://sdg.csail.mit.edu/pubs/2005/oopsla05-dsm.pdf.</description>
		<content:encoded><![CDATA[<p>Looking forward to future postings from you regarding maintenance of system structure using DSMs. Here is a paper which show how DSMs can be used to represent and maintain the architecture of large scale software: <a href="http://sdg.csail.mit.edu/pubs/2005/oopsla05-dsm.pdf" rel="nofollow">http://sdg.csail.mit.edu/pubs/.....05-dsm.pdf</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Agile Management by David Anderson</title>
		<link>http://leansoftwareengineering.com/2009/02/09/representation-of-structure/comment-page-1/#comment-4949</link>
		<dc:creator>Agile Management by David Anderson</dc:creator>
		<pubDate>Mon, 02 Mar 2009 16:44:36 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/?p=994#comment-4949</guid>
		<description>&lt;strong&gt;Lean &amp; Kanban 2009 - Draft Program...&lt;/strong&gt;

I&#039;ve been busy finalizing the speaker roster and program for the Lean &amp; Kanban 2009 Conference...</description>
		<content:encoded><![CDATA[<p><strong>Lean &amp; Kanban 2009 &#8211; Draft Program&#8230;</strong></p>
<p>I&#39;ve been busy finalizing the speaker roster and program for the Lean &amp; Kanban 2009 Conference&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Martin Jul</title>
		<link>http://leansoftwareengineering.com/2009/02/09/representation-of-structure/comment-page-1/#comment-4769</link>
		<dc:creator>Martin Jul</dc:creator>
		<pubDate>Mon, 09 Feb 2009 23:42:58 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/?p=994#comment-4769</guid>
		<description>It&#039;s nice to see your interest in DSM. 

I like to use it to explain why projects so often go wrong, why iterations are good (shorter cycles if there are cycles) etc.

Another great use is to use probabilities instead of 1 or 0 elements so that it is a matrix representing the probability distribution relating the different process steps, eg. instead of a 1 denoting &quot;requirements are the input to development&quot; we could have two inputs to dev &quot;70% requirements to dev, and 30% requirements changes to dev from &#039;oh that&#039;s not what I wanted&#039; downstream. This can be used to calculate the ratio of work and rework and explain the high cost of change - in fact, even in simple models with many steps there is a dramatic difference between operating the steps at a defect rate of 10% and 1%, since the probability of staying on the correct-first-time-through path is very low until the defect rate is reined in.

Get in touch if you would like to know more - I have some models that I could post if you are interested.

All the best,
Martin</description>
		<content:encoded><![CDATA[<p>It&#8217;s nice to see your interest in DSM. </p>
<p>I like to use it to explain why projects so often go wrong, why iterations are good (shorter cycles if there are cycles) etc.</p>
<p>Another great use is to use probabilities instead of 1 or 0 elements so that it is a matrix representing the probability distribution relating the different process steps, eg. instead of a 1 denoting &#8220;requirements are the input to development&#8221; we could have two inputs to dev &#8220;70% requirements to dev, and 30% requirements changes to dev from &#8216;oh that&#8217;s not what I wanted&#8217; downstream. This can be used to calculate the ratio of work and rework and explain the high cost of change &#8211; in fact, even in simple models with many steps there is a dramatic difference between operating the steps at a defect rate of 10% and 1%, since the probability of staying on the correct-first-time-through path is very low until the defect rate is reined in.</p>
<p>Get in touch if you would like to know more &#8211; I have some models that I could post if you are interested.</p>
<p>All the best,<br />
Martin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dew Drop - February 9, 2009 &#124; Alvin Ashcraft's Morning Dew</title>
		<link>http://leansoftwareengineering.com/2009/02/09/representation-of-structure/comment-page-1/#comment-4768</link>
		<dc:creator>Dew Drop - February 9, 2009 &#124; Alvin Ashcraft's Morning Dew</dc:creator>
		<pubDate>Mon, 09 Feb 2009 14:20:20 +0000</pubDate>
		<guid isPermaLink="false">http://leansoftwareengineering.com/?p=994#comment-4768</guid>
		<description>[...] Representation of Structure (Corey Ladas) [...]</description>
		<content:encoded><![CDATA[<p>[...] Representation of Structure (Corey Ladas) [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Dynamic Page Served (once) in 0.410 seconds -->

