<?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: Resilience Explained By Buzz Holling</title>
	<atom:link href="http://www.projectshrink.com/resilience-explained-by-buzz-holling-855.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.projectshrink.com/resilience-explained-by-buzz-holling-855.html</link>
	<description>Welcome To Shrinkonia.</description>
	<lastBuildDate>Sun, 20 May 2012 21:13:21 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Travelay</title>
		<link>http://www.projectshrink.com/resilience-explained-by-buzz-holling-855.html#comment-926</link>
		<dc:creator>Travelay</dc:creator>
		<pubDate>Sat, 20 Mar 2010 14:12:19 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=855#comment-926</guid>
		<description>Interesting to see how the ideas in Ecology can be applied to project management - thanks for sharing!</description>
		<content:encoded><![CDATA[<p>Interesting to see how the ideas in Ecology can be applied to project management &#8211; thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Meditopia Terms</title>
		<link>http://www.projectshrink.com/resilience-explained-by-buzz-holling-855.html#comment-925</link>
		<dc:creator>Meditopia Terms</dc:creator>
		<pubDate>Mon, 02 Mar 2009 15:50:41 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=855#comment-925</guid>
		<description>Thanks for a great post, it was nice to read through and watch the video.&lt;br&gt;It is a brainwashing post by you and I got to learn a lot.&lt;br&gt;I am starter in the project mgmt. arena and have a couple of projects in my bag but everyday has brought new knowledge and specially with professional people like you sharing stuff..</description>
		<content:encoded><![CDATA[<p>Thanks for a great post, it was nice to read through and watch the video.<br />It is a brainwashing post by you and I got to learn a lot.<br />I am starter in the project mgmt. arena and have a couple of projects in my bag but everyday has brought new knowledge and specially with professional people like you sharing stuff..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bas</title>
		<link>http://www.projectshrink.com/resilience-explained-by-buzz-holling-855.html#comment-924</link>
		<dc:creator>Bas</dc:creator>
		<pubDate>Tue, 02 Dec 2008 15:26:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=855#comment-924</guid>
		<description>Hi Andrew, fair question … resilience is an idea. Panarchy is a generic model, so the concept itself doesn’t provide concrete steps. For me personally the attractiveness lies within the fact that it covers a wide angle view and is relatively simple. It tells you to not only look at the project, but also to the organization and the individual, it tells you that breakdown is almost inevitable, but the system can restore itself.
It explains effects of the culture of the organization on a project, it explains that it is ok to have individual employees let go of steam (but avoid having the whole team in stress). It explains the need for a breakdown (sometimes). Samples at the end of this post:
http://www.basdebaar.com/panarchy-analyzing-complexity-projects-312.html
Try to avoid having scarce resources. Overcapacity provides better resilience.
“On demand” services like Platform As A Service provide resilience as they shorten lead times and eliminate it as a scarce resource. Concepts like virtual testing provide the same idea
http://www.basdebaar.com/virtual-testing-413.html
I think you get the point. It opens up a (potential new) way of looking at things.

But I guess it will take another year or so to find the right words :)</description>
		<content:encoded><![CDATA[<p>Hi Andrew, fair question … resilience is an idea. Panarchy is a generic model, so the concept itself doesn’t provide concrete steps. For me personally the attractiveness lies within the fact that it covers a wide angle view and is relatively simple. It tells you to not only look at the project, but also to the organization and the individual, it tells you that breakdown is almost inevitable, but the system can restore itself.<br />
It explains effects of the culture of the organization on a project, it explains that it is ok to have individual employees let go of steam (but avoid having the whole team in stress). It explains the need for a breakdown (sometimes). Samples at the end of this post:<br />
<a href="http://www.basdebaar.com/panarchy-analyzing-complexity-projects-312.html" rel="nofollow">http://www.basdebaar.com/panarchy-analyzing-complexity-projects-312.html</a><br />
Try to avoid having scarce resources. Overcapacity provides better resilience.<br />
“On demand” services like Platform As A Service provide resilience as they shorten lead times and eliminate it as a scarce resource. Concepts like virtual testing provide the same idea<br />
<a href="http://www.basdebaar.com/virtual-testing-413.html" rel="nofollow">http://www.basdebaar.com/virtual-testing-413.html</a><br />
I think you get the point. It opens up a (potential new) way of looking at things.</p>
<p>But I guess it will take another year or so to find the right words <img src='http://www.projectshrink.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Sparks</title>
		<link>http://www.projectshrink.com/resilience-explained-by-buzz-holling-855.html#comment-923</link>
		<dc:creator>Andrew Sparks</dc:creator>
		<pubDate>Tue, 02 Dec 2008 11:02:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=855#comment-923</guid>
		<description>Very interesting - esp the video on Buzz Holling.
Where I get to fairly quickly though is: OK - what concrete steps can you take in your project today?
The follow the sun idea is a good one but not applicable everywhere.
Variety is one aspect. Eg your ability as PM to cope with different kinds of people on yr team and the create an environment where they surface the issues (and solve them) in ways that are effective for them. Variety also guards against groupthink/incestuous amplification</description>
		<content:encoded><![CDATA[<p>Very interesting &#8211; esp the video on Buzz Holling.<br />
Where I get to fairly quickly though is: OK &#8211; what concrete steps can you take in your project today?<br />
The follow the sun idea is a good one but not applicable everywhere.<br />
Variety is one aspect. Eg your ability as PM to cope with different kinds of people on yr team and the create an environment where they surface the issues (and solve them) in ways that are effective for them. Variety also guards against groupthink/incestuous amplification</p>
]]></content:encoded>
	</item>
</channel>
</rss>

