<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.1-alpha" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Sad XP story I heard</title>
	<link>http://tottinge.blogsome.com/2006/12/08/sad-xp-story-i-heard/</link>
	<description>Tim Ottinger on Christianity, freedom, software, podcasts, and really hot-looking guitars.</description>
	<pubDate>Sat, 11 Oct 2008 11:22:16 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.1-alpha</generator>

	<item>
		<title>by: Kris Cook</title>
		<link>http://tottinge.blogsome.com/2006/12/08/sad-xp-story-i-heard/#comment-455</link>
		<pubDate>Fri, 08 Dec 2006 15:07:49 +0000</pubDate>
		<guid>http://tottinge.blogsome.com/2006/12/08/sad-xp-story-i-heard/#comment-455</guid>
					<description>Yeah, it's a case where you can see both sides.  If you have a large organizations with different teams and groups working toward a common end product, you have to have a standard methodology.  Especially with Sarbannes-Oxley; it mandates that you MUST have a standard SDLC across your organization.  Of course, you can define your organization at a smaller level, but not smaller than an application.

What REALLY hurts is when you have a method that does't work, and the whole organization knows it and decides to address it.  But then, they put the same people in charge of the NEW methodology that are most vested inthe OLD methodology, so they buy neat new tools and hire expensive consultants, but wind up shoe-horning everything back into the old model. Which of course is WORSE, so upper management thinks the new methodology is a bust, even though it wasn't ever used.

Can you tell I've been there?  Repeatedly?  Sigh...</description>
		<content:encoded><![CDATA[	<p>Yeah, it&#8217;s a case where you can see both sides.  If you have a large organizations with different teams and groups working toward a common end product, you have to have a standard methodology.  Especially with Sarbannes-Oxley; it mandates that you MUST have a standard SDLC across your organization.  Of course, you can define your organization at a smaller level, but not smaller than an application.</p>
	<p>What REALLY hurts is when you have a method that does&#8217;t work, and the whole organization knows it and decides to address it.  But then, they put the same people in charge of the NEW methodology that are most vested inthe OLD methodology, so they buy neat new tools and hire expensive consultants, but wind up shoe-horning everything back into the old model. Which of course is WORSE, so upper management thinks the new methodology is a bust, even though it wasn&#8217;t ever used.</p>
	<p>Can you tell I&#8217;ve been there?  Repeatedly?  Sigh&#8230;
</p>
]]></content:encoded>
				</item>
	<item>
		<title>by: Steve</title>
		<link>http://tottinge.blogsome.com/2006/12/08/sad-xp-story-i-heard/#comment-454</link>
		<pubDate>Fri, 08 Dec 2006 12:25:36 +0000</pubDate>
		<guid>http://tottinge.blogsome.com/2006/12/08/sad-xp-story-i-heard/#comment-454</guid>
					<description>I agree Tim.  Both sides could fight it out for hours/days/weeks on who is right.  Ultimately though, it comes down to what the boss wants.  In a world where communication is key, leaving out the boss isn't such a good idea.</description>
		<content:encoded><![CDATA[	<p>I agree Tim.  Both sides could fight it out for hours/days/weeks on who is right.  Ultimately though, it comes down to what the boss wants.  In a world where communication is key, leaving out the boss isn&#8217;t such a good idea.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
