On Friday, December 17, 2004, at 1:36:02 PM, Steve Berczuk wrote:
>> Beck said a long time ago that he felt that the existence of two
>> roles, customer and programmer, in XP was a flaw, but that he
>> couldn't see how to get rid of it. I tend to agree.
>>
>> In a smoothly-running team, the roles blur to an amazing degree, and
>> in that blurring lies power.
> Isn't this a bit of a bootstrapping problem? SOMEONE needs to have a
> need that starts the project? And someone needs to arbitrate when
> there are choices that seem equally good.... I agree that the great
> thing is when everyone seems like they are on the same team (which
> they, in fact, are...)...
Yes ... I imagine that's why we can't get rid of the distinction.
But I also imagine that I understand why Mr Beck felt it was a
"flaw" in the design of XP.
> (On a related note, the idea of Development, QA, and Release
> Engineering Teams with handoffs between them is also a source of
> problems in many organizations... while there may well be some degree
> of specialization, everyone needs to own the resulting product...)
Yes, indeed.
Ron Jeffries
www.XProgramming.com
One test is worth a thousand expert opinions.
-- Bill Nye (The Science Guy)
To Post a message, send it to: [EMAIL PROTECTED]
To Unsubscribe, send a blank message to: [EMAIL PROTECTED]
ad-free courtesy of objectmentor.com
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/extremeprogramming/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
