<?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 for Agile Business Continuity</title>
	<atom:link href="http://www.agilecontinuity.org/comments/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.agilecontinuity.org</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Sat, 17 Dec 2011 08:14:29 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>Comment on BCP Documentation by Rachel Cade (scenario-based continuity exercise specialist)</title>
		<link>http://www.agilecontinuity.org/bcp-documentation/comment-page-1/#comment-98</link>
		<dc:creator>Rachel Cade (scenario-based continuity exercise specialist)</dc:creator>
		<pubDate>Sat, 17 Dec 2011 08:14:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilecontinuity.org/?p=1154#comment-98</guid>
		<description>Ok, I&#039;m going to confess that every year I do the rounds at the BCI conference and look at the software, and every year I fail to find anything that I can wholeheartedly recommend to clients.

My worry with software based planning is that it has the ability to become a form-filling exercise rather than a planning process.  

I&#039;ve recently seen one system that I think might be useful if it was tweaked more but, even then, I wonder if I just want it to work because my companies (when I work in-house) and clients (when external) really want me to have a recommendation.

Until I have one I stand by my notion that it&#039;s better to have a real plan done in plain old word than a beautiful and organised one that was created after a form filling exercise in a manner that those who used it haven&#039;t truly thought through their step-by-step arrangements and checklists...

Which software might you recommend I look at next?!</description>
		<content:encoded><![CDATA[<p>Ok, I&#8217;m going to confess that every year I do the rounds at the BCI conference and look at the software, and every year I fail to find anything that I can wholeheartedly recommend to clients.</p>
<p>My worry with software based planning is that it has the ability to become a form-filling exercise rather than a planning process.  </p>
<p>I&#8217;ve recently seen one system that I think might be useful if it was tweaked more but, even then, I wonder if I just want it to work because my companies (when I work in-house) and clients (when external) really want me to have a recommendation.</p>
<p>Until I have one I stand by my notion that it&#8217;s better to have a real plan done in plain old word than a beautiful and organised one that was created after a form filling exercise in a manner that those who used it haven&#8217;t truly thought through their step-by-step arrangements and checklists&#8230;</p>
<p>Which software might you recommend I look at next?!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on We&#8217;ve Moved To Google Apps by Rachel Cade (scenario-based continuity exercise specialist)</title>
		<link>http://www.agilecontinuity.org/weve-moved-to-google-apps/comment-page-1/#comment-97</link>
		<dc:creator>Rachel Cade (scenario-based continuity exercise specialist)</dc:creator>
		<pubDate>Sat, 17 Dec 2011 08:09:48 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilecontinuity.org/?p=1151#comment-97</guid>
		<description>Hello, Like Marc I&#039;d love an update to this post, if you&#039;ve time?  

How do you manage your business continuity issues around up-time of your software around google apps?  Are you able to negotiate SLAs with them if you pay for the apps or are you using the free version.

Really would be genuinely interested to learn more about how you&#039;ve found the switch in relation to you BC expertise.

Rachel</description>
		<content:encoded><![CDATA[<p>Hello, Like Marc I&#8217;d love an update to this post, if you&#8217;ve time?  </p>
<p>How do you manage your business continuity issues around up-time of your software around google apps?  Are you able to negotiate SLAs with them if you pay for the apps or are you using the free version.</p>
<p>Really would be genuinely interested to learn more about how you&#8217;ve found the switch in relation to you BC expertise.</p>
<p>Rachel</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Purpose of Business Continuity by Rachel Cade (scenario-based continuity exercise specialist)</title>
		<link>http://www.agilecontinuity.org/the-purpose-of-business-continuity/comment-page-1/#comment-93</link>
		<dc:creator>Rachel Cade (scenario-based continuity exercise specialist)</dc:creator>
		<pubDate>Fri, 04 Nov 2011 12:33:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilecontinuity.org/?p=1156#comment-93</guid>
		<description>Thanks for this.  I&#039;m just writing a brief for someone who wants me to convince their board they need a continuity plan and I&#039;ll use some of these points, if I may.  I think I&#039;m going for reverse psychology though and starting with &#039;here&#039;s some reasons why you might not need a plan&#039;!</description>
		<content:encoded><![CDATA[<p>Thanks for this.  I&#8217;m just writing a brief for someone who wants me to convince their board they need a continuity plan and I&#8217;ll use some of these points, if I may.  I think I&#8217;m going for reverse psychology though and starting with &#8216;here&#8217;s some reasons why you might not need a plan&#8217;!</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Purpose of Business Continuity by Shafiq Hamid</title>
		<link>http://www.agilecontinuity.org/the-purpose-of-business-continuity/comment-page-1/#comment-91</link>
		<dc:creator>Shafiq Hamid</dc:creator>
		<pubDate>Wed, 18 May 2011 13:06:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilecontinuity.org/?p=1156#comment-91</guid>
		<description>Very good post.

We have a debate at one of the big clients - they is a battle going on as to where BCM should be i.e. ownership.

As a best practice I believe that BCM should always be outside IT. 

If it must be within IT - where should it be? Would love some comments on this.</description>
		<content:encoded><![CDATA[<p>Very good post.</p>
<p>We have a debate at one of the big clients &#8211; they is a battle going on as to where BCM should be i.e. ownership.</p>
<p>As a best practice I believe that BCM should always be outside IT. </p>
<p>If it must be within IT &#8211; where should it be? Would love some comments on this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Risk Assessment &#8211; Measuring Resilience Part 4 by replacement workers BCP</title>
		<link>http://www.agilecontinuity.org/risk-assessment-measuring-resilience-part-4/comment-page-1/#comment-86</link>
		<dc:creator>replacement workers BCP</dc:creator>
		<pubDate>Thu, 06 Jan 2011 20:01:00 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilecontinuity.org/?p=667#comment-86</guid>
		<description>Interesting post. You could teach a class on this stuff!

I do have one question though, how does one &quot;address risks faster than they grow? 

In my experience, I always opt for a proactive approach to risk management, and in most cases -- conflicts are extinguished before they become full-blown fires. However, what is your recourse when risk management backfires?</description>
		<content:encoded><![CDATA[<p>Interesting post. You could teach a class on this stuff!</p>
<p>I do have one question though, how does one &#8220;address risks faster than they grow? </p>
<p>In my experience, I always opt for a proactive approach to risk management, and in most cases &#8212; conflicts are extinguished before they become full-blown fires. However, what is your recourse when risk management backfires?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on An Interesting Thing Happened On The Way To 2010 by replacement workers BCP</title>
		<link>http://www.agilecontinuity.org/an-interesting-thing-happened-on-the-way-to-2010/comment-page-1/#comment-85</link>
		<dc:creator>replacement workers BCP</dc:creator>
		<pubDate>Thu, 06 Jan 2011 19:55:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilecontinuity.org/?p=1143#comment-85</guid>
		<description>A GTD Attitude, Great relationships with employees, clients and partners -- all proactive things to do that eliminate problems before they ever arise.

I like your focus here....it&#039;s proactive as opposed to reactive.</description>
		<content:encoded><![CDATA[<p>A GTD Attitude, Great relationships with employees, clients and partners &#8212; all proactive things to do that eliminate problems before they ever arise.</p>
<p>I like your focus here&#8230;.it&#8217;s proactive as opposed to reactive.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on We&#8217;ve Moved To Google Apps by Marc</title>
		<link>http://www.agilecontinuity.org/weve-moved-to-google-apps/comment-page-1/#comment-84</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Thu, 06 Jan 2011 19:50:51 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilecontinuity.org/?p=1151#comment-84</guid>
		<description>Well, it might not have much to do with business continuity BUT how can storing your information on the &quot;cloud&quot; have a positive impact on continuity?

Maybe fodder for a future post?

Keep up the good work.</description>
		<content:encoded><![CDATA[<p>Well, it might not have much to do with business continuity BUT how can storing your information on the &#8220;cloud&#8221; have a positive impact on continuity?</p>
<p>Maybe fodder for a future post?</p>
<p>Keep up the good work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on BCP Documentation by Marc</title>
		<link>http://www.agilecontinuity.org/bcp-documentation/comment-page-1/#comment-83</link>
		<dc:creator>Marc</dc:creator>
		<pubDate>Thu, 06 Jan 2011 19:45:01 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilecontinuity.org/?p=1154#comment-83</guid>
		<description>Very good points! 

I do have one thing to add though. You mentioned that software CAN in fact be a boon to business continuity, and I agree with you wholeheartedly that it must be the &quot;right&quot; software. Do you think, though, that software can often become a crutch that gets in the way of purely inter-personal methods of BCP implementation?</description>
		<content:encoded><![CDATA[<p>Very good points! </p>
<p>I do have one thing to add though. You mentioned that software CAN in fact be a boon to business continuity, and I agree with you wholeheartedly that it must be the &#8220;right&#8221; software. Do you think, though, that software can often become a crutch that gets in the way of purely inter-personal methods of BCP implementation?</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on The Purpose of Business Continuity by Erik</title>
		<link>http://www.agilecontinuity.org/the-purpose-of-business-continuity/comment-page-1/#comment-82</link>
		<dc:creator>Erik</dc:creator>
		<pubDate>Wed, 08 Dec 2010 15:16:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilecontinuity.org/?p=1156#comment-82</guid>
		<description>Very interesting post - and right on the money with plans generating &quot;heat but very little light&quot;.  A plan without training to embed it within an organization is poorly planned. I am a little confused with the way that you apply some of the terms in this post, however. 

By predictability, I think you are referring to &quot;continuity&quot;. Executives want the business to keep going in the face of a disaster, with business not being interrupted.  I would be very concerned for an organization that felt it was resilient because it was able to accurately predict anything that might happen to it. This smacks of the turkey in Taleb&#039;s &quot;The Black Swan&quot; which is fed every day by the farmer each morning. This pattern establishes its expectation/prediction that this will continue indefinitely, until one fateful Thanksgiving when the turkey has a &quot;revision of belief&quot;. 

The all hazards approach can help to improve resilience, but is designed under the assumption that our ability to predict hazards is flawed. An agile organization with a clear business continuity plan may identify specific hazards that historically have a greater chance of occurring, but will also need to be prepared for those that cannot be predicted.</description>
		<content:encoded><![CDATA[<p>Very interesting post &#8211; and right on the money with plans generating &#8220;heat but very little light&#8221;.  A plan without training to embed it within an organization is poorly planned. I am a little confused with the way that you apply some of the terms in this post, however. </p>
<p>By predictability, I think you are referring to &#8220;continuity&#8221;. Executives want the business to keep going in the face of a disaster, with business not being interrupted.  I would be very concerned for an organization that felt it was resilient because it was able to accurately predict anything that might happen to it. This smacks of the turkey in Taleb&#8217;s &#8220;The Black Swan&#8221; which is fed every day by the farmer each morning. This pattern establishes its expectation/prediction that this will continue indefinitely, until one fateful Thanksgiving when the turkey has a &#8220;revision of belief&#8221;. </p>
<p>The all hazards approach can help to improve resilience, but is designed under the assumption that our ability to predict hazards is flawed. An agile organization with a clear business continuity plan may identify specific hazards that historically have a greater chance of occurring, but will also need to be prepared for those that cannot be predicted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>Comment on Blogosphere Focus: Ken Simpson&#039;s Contemplating by &#8230; 525,600 minutes :: Contemplating &#8230;</title>
		<link>http://www.agilecontinuity.org/blogosphere-focus-ken-simpsons-contemplating/comment-page-1/#comment-80</link>
		<dc:creator>&#8230; 525,600 minutes :: Contemplating &#8230;</dc:creator>
		<pubDate>Fri, 19 Nov 2010 13:25:28 +0000</pubDate>
		<guid isPermaLink="false">http://www.agilecontinuity.org/?p=797#comment-80</guid>
		<description>[...] Paul James, Agile Continuity Sadly Paul seems to no longer be posting on his blog, pity as there are few quality thinkers and writers in this space. [...]</description>
		<content:encoded><![CDATA[<p>[...] Paul James, Agile Continuity Sadly Paul seems to no longer be posting on his blog, pity as there are few quality thinkers and writers in this space. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

