<?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: How To Convince An Organization To Go Agile?</title>
	<atom:link href="http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html</link>
	<description>Welcome To Shrinkonia.</description>
	<lastBuildDate>Sun, 13 May 2012 19:09:52 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Bas de Baar</title>
		<link>http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html#comment-1457</link>
		<dc:creator>Bas de Baar</dc:creator>
		<pubDate>Sun, 06 Jun 2010 10:09:00 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1627#comment-1457</guid>
		<description>Hi Dave, thanks for the link. I like the article. Good points. The question is of course how are you trying to convince? it depends on the type of organization I guess. Some would require scientific studies for every claim :)</description>
		<content:encoded><![CDATA[<p>Hi Dave, thanks for the link. I like the article. Good points. The question is of course how are you trying to convince? it depends on the type of organization I guess. Some would require scientific studies for every claim <img src='http://www.projectshrink.com/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave Moran</title>
		<link>http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html#comment-1456</link>
		<dc:creator>Dave Moran</dc:creator>
		<pubDate>Sun, 06 Jun 2010 09:49:58 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1627#comment-1456</guid>
		<description>Bas,

I recently published an article on the &quot;Top 10 Reasons to Use Agile Development.&quot; A reprint can be found on my blog at: http://www.softwareresults.us/2010/06/what-is-better-about-agile-development.html. I&#039;d be interested in what you and your readers have to say about this. It is my attempt to justify/convince organizations that they should go Agile.</description>
		<content:encoded><![CDATA[<p>Bas,</p>
<p>I recently published an article on the &#8220;Top 10 Reasons to Use Agile Development.&#8221; A reprint can be found on my blog at: <a href="http://www.softwareresults.us/2010/06/what-is-better-about-agile-development.html" rel="nofollow">http://www.softwareresults.us/2010/06/what-is-better-about-agile-development.html</a>. I&#8217;d be interested in what you and your readers have to say about this. It is my attempt to justify/convince organizations that they should go Agile.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Emmanuel</title>
		<link>http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html#comment-1455</link>
		<dc:creator>Emmanuel</dc:creator>
		<pubDate>Tue, 14 Jul 2009 13:45:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1627#comment-1455</guid>
		<description>Dear B.
 Thank you for a your message.</description>
		<content:encoded><![CDATA[<p>Dear B.<br />
 Thank you for a your message.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bas de Baar</title>
		<link>http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html#comment-1454</link>
		<dc:creator>Bas de Baar</dc:creator>
		<pubDate>Fri, 19 Jun 2009 16:18:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1627#comment-1454</guid>
		<description>Hi Maame,

It depends on what you want to achieve and where you are located.

You can drop me a mail if you want. bas- at- projectshrink . com

Cheers
Bas</description>
		<content:encoded><![CDATA[<p>Hi Maame,</p>
<p>It depends on what you want to achieve and where you are located.</p>
<p>You can drop me a mail if you want. bas- at- projectshrink . com</p>
<p>Cheers<br />
Bas</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bas de Baar</title>
		<link>http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html#comment-1453</link>
		<dc:creator>Bas de Baar</dc:creator>
		<pubDate>Thu, 18 Jun 2009 07:11:26 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1627#comment-1453</guid>
		<description>@Paul, Diwant, Angelo: yes, yes! thanks for the addition.

@Craig: it almost is like &quot;plan to throw one away&quot;... a project that is. First do a project agile style to create transparency, flush the pipes so you know where your trouble spots will be?</description>
		<content:encoded><![CDATA[<p>@Paul, Diwant, Angelo: yes, yes! thanks for the addition.</p>
<p>@Craig: it almost is like &#8220;plan to throw one away&#8221;&#8230; a project that is. First do a project agile style to create transparency, flush the pipes so you know where your trouble spots will be?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: MAAME BOATENG</title>
		<link>http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html#comment-1452</link>
		<dc:creator>MAAME BOATENG</dc:creator>
		<pubDate>Wed, 17 Jun 2009 15:47:09 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1627#comment-1452</guid>
		<description>I JUST COMPLETED A PROGRAM IN PROJECT MANAGEMENT.

WHAT DO I NEED FURTHER.

THANX.</description>
		<content:encoded><![CDATA[<p>I JUST COMPLETED A PROGRAM IN PROJECT MANAGEMENT.</p>
<p>WHAT DO I NEED FURTHER.</p>
<p>THANX.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Craig</title>
		<link>http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html#comment-1451</link>
		<dc:creator>Craig</dc:creator>
		<pubDate>Wed, 17 Jun 2009 13:54:59 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1627#comment-1451</guid>
		<description>For what it&#039;s worth I think Jesse&#039;s espnse is the most important answer you got Bas.

How do you addres a ssytem that is ging to make you work harder and remove the ability to blame someone else?

I think: Buy the model and your whole operation will improve osmotically</description>
		<content:encoded><![CDATA[<p>For what it&#8217;s worth I think Jesse&#8217;s espnse is the most important answer you got Bas.</p>
<p>How do you addres a ssytem that is ging to make you work harder and remove the ability to blame someone else?</p>
<p>I think: Buy the model and your whole operation will improve osmotically</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Angelo</title>
		<link>http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html#comment-1450</link>
		<dc:creator>Angelo</dc:creator>
		<pubDate>Wed, 17 Jun 2009 13:10:30 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1627#comment-1450</guid>
		<description>Bas,

I think one primary reason why a lot of organizations (especially the big ones) are so tied up with doing software and IT projects in the traditional way instead of better agile methods is because the former tends to give them a sense of having an &quot;actual&quot; tight schedule which should be met.  Most leaders, PMs, senior level management have not been fully exposed on the principles of what and how makes agile tick that they do not want to simply jump on the bandwagon - taking into consideration as well that they felt secure and had found success (to some degree) using traditional methodologies.

I think we might see a further shift to agile methodologies when people who would be later assuming more senior roles are the ones who have used them in their projects.  These people know the values offered by going agile to an organization and have the actual drive to implement them.  But as of the moment, with most top levels in organization still proud of how they do things, then it applies they are most likely not to employ and embrace change.</description>
		<content:encoded><![CDATA[<p>Bas,</p>
<p>I think one primary reason why a lot of organizations (especially the big ones) are so tied up with doing software and IT projects in the traditional way instead of better agile methods is because the former tends to give them a sense of having an &#8220;actual&#8221; tight schedule which should be met.  Most leaders, PMs, senior level management have not been fully exposed on the principles of what and how makes agile tick that they do not want to simply jump on the bandwagon &#8211; taking into consideration as well that they felt secure and had found success (to some degree) using traditional methodologies.</p>
<p>I think we might see a further shift to agile methodologies when people who would be later assuming more senior roles are the ones who have used them in their projects.  These people know the values offered by going agile to an organization and have the actual drive to implement them.  But as of the moment, with most top levels in organization still proud of how they do things, then it applies they are most likely not to employ and embrace change.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Diwant Vaidya</title>
		<link>http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html#comment-1449</link>
		<dc:creator>Diwant Vaidya</dc:creator>
		<pubDate>Thu, 11 Jun 2009 17:50:16 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1627#comment-1449</guid>
		<description>@Jesse Greater accountability has been a snag for our customers, especially when we show project chunks in red/yellow/green status colors.  I have a feeling that the lack of transparency and accountability that 300 line Gantt charts and task lists provide are a big reason why they still survive.

I think Jesse&#039;s comment directly applied to me.  I have seen the situations described by the other two, but haven&#039;t seen it with our customers yet.</description>
		<content:encoded><![CDATA[<p>@Jesse Greater accountability has been a snag for our customers, especially when we show project chunks in red/yellow/green status colors.  I have a feeling that the lack of transparency and accountability that 300 line Gantt charts and task lists provide are a big reason why they still survive.</p>
<p>I think Jesse&#8217;s comment directly applied to me.  I have seen the situations described by the other two, but haven&#8217;t seen it with our customers yet.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Paul Boos</title>
		<link>http://www.projectshrink.com/how-to-convince-an-organization-to-go-agile-1627.html#comment-1448</link>
		<dc:creator>Paul Boos</dc:creator>
		<pubDate>Wed, 10 Jun 2009 17:01:22 +0000</pubDate>
		<guid isPermaLink="false">http://blog.softwareprojects.org/?p=1627#comment-1448</guid>
		<description>Bas, great question and I loved the answers you got back.  Let me throw a reason larger organizations and in particularly the Government resists this kind of movement; frequently using the renegade argument.

Large organizations worry about compliance; they have enterprise architecture, legal, auditing, security, etc. stakeholders they have to make happy and in some cases these stakeholders actually displace the customers of the systems being built in  their importance.  It has taken forever for organizations to figure out how to comply: how to do EVM, how to show they have an enterprise architecture, how to develop the documents that get the system accredited, etc..  To figure out how to do this stuff for yet another approach is unfathomably hard, since they can&#039;t keep up with the changes these stakeholders have now, how will they do it supporting a different approach.

In reality, Agile would actually make this much easier to both accomplish and to measure the impact of these additional stakeholder effects, but the bureaucracy of the large often doesn&#039;t want to change from known to unknown.</description>
		<content:encoded><![CDATA[<p>Bas, great question and I loved the answers you got back.  Let me throw a reason larger organizations and in particularly the Government resists this kind of movement; frequently using the renegade argument.</p>
<p>Large organizations worry about compliance; they have enterprise architecture, legal, auditing, security, etc. stakeholders they have to make happy and in some cases these stakeholders actually displace the customers of the systems being built in  their importance.  It has taken forever for organizations to figure out how to comply: how to do EVM, how to show they have an enterprise architecture, how to develop the documents that get the system accredited, etc..  To figure out how to do this stuff for yet another approach is unfathomably hard, since they can&#8217;t keep up with the changes these stakeholders have now, how will they do it supporting a different approach.</p>
<p>In reality, Agile would actually make this much easier to both accomplish and to measure the impact of these additional stakeholder effects, but the bureaucracy of the large often doesn&#8217;t want to change from known to unknown.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

