I agree. A different way to make it incremental is to just convert one team
doing one project or subproject. Adjusting XP to the business processes
and cultures (or vice-versa) can be resolved in the small, lessons can be
learned, and success can be demonstrated before scaling to an entire
department or company.
-----Original Message-----
From: Dominic Williams [mailto:[EMAIL PROTECTED]
Sent: Wed 12/1/2004 1:40 AM
To: [EMAIL PROTECTED]
Cc:
Subject: Re: [XP] Education
Gary wrote:
> In the absence of a hatchet-wielding manager, change
> usually needs to be introduced one step at a time.
> That means pick one XP practice, and get that
> securely anchored before pushing on the next.
That approach may be suitable in some circumstances,
but personally I am a proponent of the opposite
approach (switching to full XP all of a sudden), when
it is possible.
XP's practices are very interdependent: doing some of
them may be difficult and/or pointless without the
balance of others.
Regards,
Dominic Williams
http://www.dominicwilliams.net
[Non-text portions of this message have been removed]
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/
