<?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: Why I speak of Agile/Scrum and not XP &#8211; or Language matters</title>
	<atom:link href="http://agilepainrelief.com/notesfromatooluser/2008/11/why-i-speak-of-agilescrum-and-not-xp.html/feed" rel="self" type="application/rss+xml" />
	<link>http://agilepainrelief.com/notesfromatooluser/2008/11/why-i-speak-of-agilescrum-and-not-xp.html?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=why-i-speak-of-agilescrum-and-not-xp</link>
	<description>Best practices for your goals</description>
	<lastBuildDate>Sat, 19 May 2012 03:39:00 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Adam Sroka</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2008/11/why-i-speak-of-agilescrum-and-not-xp.html/comment-page-1#comment-126</link>
		<dc:creator>Adam Sroka</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2008/11/why-i-speak-of-agilescrum-and-not-xp/#comment-126</guid>
		<description>AFAIK, the term &quot;engineering practices&quot; is a relatively new one and came out of the Scrum community. I first recalling hearing it used by Tobias Mayer.

All of the practices that make up XP come from somewhere else. XP itself was an evolution of the practices Kent Beck was using at the time he was working the Chrysler Comprehensive Compensation project. The term Extreme Programming referred to the idea of taking a certain set of practices which worked really well, and doing them all, together, all the time, to the exclusion of anything else. Thus taking the things that work and pushing them to the extreme.

XP may sound a bit... well, extreme. However, I find that when people understand the meaning of the term they are less likely to object to it.

I was on the XP list back in 2002/2003. As for zealotry I plead the Fifth.
</description>
		<content:encoded><![CDATA[<p>AFAIK, the term &#8220;engineering practices&#8221; is a relatively new one and came out of the Scrum community. I first recalling hearing it used by Tobias Mayer.</p>
<p>All of the practices that make up XP come from somewhere else. XP itself was an evolution of the practices Kent Beck was using at the time he was working the Chrysler Comprehensive Compensation project. The term Extreme Programming referred to the idea of taking a certain set of practices which worked really well, and doing them all, together, all the time, to the exclusion of anything else. Thus taking the things that work and pushing them to the extreme.</p>
<p>XP may sound a bit&#8230; well, extreme. However, I find that when people understand the meaning of the term they are less likely to object to it.</p>
<p>I was on the XP list back in 2002/2003. As for zealotry I plead the Fifth.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Alan</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2008/11/why-i-speak-of-agilescrum-and-not-xp.html/comment-page-1#comment-127</link>
		<dc:creator>Alan</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2008/11/why-i-speak-of-agilescrum-and-not-xp/#comment-127</guid>
		<description>I agree. Language matters. There will always be these &quot;what&#039;s in a name?&quot; people who don&#039;t mind, and don&#039;t see why anyone else would mind. But they&#039;re wrong. Every marketer knows the choice of name is important. There was a recent blog posting about this:

http://blog.magenic.com/blogs/aarone/archive/2008/11/19/Pair-Programming-_2D00_-Marketing-FAIL.aspx

He recommends rebranding XP &quot;Collaborative Programming&quot;. I like this suggestion. I&#039;m not sure that covers all the bases, but it&#039;s a start. The problem is that are a lot of books and web pages are that use &quot;XP&quot; and &quot;extreme&quot; and other words that don&#039;t sell well, and people will be suspicious of a sudden rebranding. But I think it has to be done, slowly but surely.

</description>
		<content:encoded><![CDATA[<p>I agree. Language matters. There will always be these &#8220;what&#8217;s in a name?&#8221; people who don&#8217;t mind, and don&#8217;t see why anyone else would mind. But they&#8217;re wrong. Every marketer knows the choice of name is important. There was a recent blog posting about this:</p>
<p><a href="http://blog.magenic.com/blogs/aarone/archive/2008/11/19/Pair-Programming-_2D00_-Marketing-FAIL.aspx" rel="nofollow">http://blog.magenic.com/blogs/aarone/archive/2008/11/19/Pair-Programming-_2D00_-Marketing-FAIL.aspx</a></p>
<p>He recommends rebranding XP &#8220;Collaborative Programming&#8221;. I like this suggestion. I&#8217;m not sure that covers all the bases, but it&#8217;s a start. The problem is that are a lot of books and web pages are that use &#8220;XP&#8221; and &#8220;extreme&#8221; and other words that don&#8217;t sell well, and people will be suspicious of a sudden rebranding. But I think it has to be done, slowly but surely.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam Sroka</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2008/11/why-i-speak-of-agilescrum-and-not-xp.html/comment-page-1#comment-128</link>
		<dc:creator>Adam Sroka</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2008/11/why-i-speak-of-agilescrum-and-not-xp/#comment-128</guid>
		<description>Another thought:

What I need is a way to say, &quot;this minimal set of practices that work very well together. Not necessarily to the exclusion of anything else, but at least these.&quot; To those familiar with XP it implies a certain set of inclusive practices. If you remove any of them it is no longer XP.

What I don&#039;t like about the &quot;Scrum with Engineering Practices&quot; idea, as I have commented on my own blog, is the idea that the practices are individually and collectively optional. This leads to the idea that I can have absolutely no technical discipline at all and still call what I am doing scrum (After all, we have daily meetings.) Or, that I can introduce certain practices that I like and leave out the others. The problem being that unless I have used these practices together there is a good chance that I don&#039;t really know what I can/should get out of them.

So, I want a way to say, &quot;We do all these things, all the time. We *do not* merely do some of these things, some of the time.&quot; How do I say that? In two letters or less :-D
</description>
		<content:encoded><![CDATA[<p>Another thought:</p>
<p>What I need is a way to say, &#8220;this minimal set of practices that work very well together. Not necessarily to the exclusion of anything else, but at least these.&#8221; To those familiar with XP it implies a certain set of inclusive practices. If you remove any of them it is no longer XP.</p>
<p>What I don&#8217;t like about the &#8220;Scrum with Engineering Practices&#8221; idea, as I have commented on my own blog, is the idea that the practices are individually and collectively optional. This leads to the idea that I can have absolutely no technical discipline at all and still call what I am doing scrum (After all, we have daily meetings.) Or, that I can introduce certain practices that I like and leave out the others. The problem being that unless I have used these practices together there is a good chance that I don&#8217;t really know what I can/should get out of them.</p>
<p>So, I want a way to say, &#8220;We do all these things, all the time. We *do not* merely do some of these things, some of the time.&#8221; How do I say that? In two letters or less :-D</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Carlton Nettleton</title>
		<link>http://agilepainrelief.com/notesfromatooluser/2008/11/why-i-speak-of-agilescrum-and-not-xp.html/comment-page-1#comment-129</link>
		<dc:creator>Carlton Nettleton</dc:creator>
		<pubDate>Tue, 30 Nov 1999 00:00:00 +0000</pubDate>
		<guid isPermaLink="false">http://agilepainrelief.com/2008/11/why-i-speak-of-agilescrum-and-not-xp/#comment-129</guid>
		<description>I seem to find the phrase &quot;Lean Programming&quot; calms people down.
</description>
		<content:encoded><![CDATA[<p>I seem to find the phrase &#8220;Lean Programming&#8221; calms people down.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

