[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: eXtreme Programming
- To: "Fuqua, Andrew (ISSAtlanta)" <AFuqua@iss.net>, vecellio@bellsouth.net, Atlanta Java Users Group <ajug-members@ajug.org>
- Subject: Re: eXtreme Programming
- From: Lee Chalupa <lchalupa@seelink.org>
- Date: Thu, 13 Nov 2003 20:00:27 -0500
- In-Reply-To: <632B4A260DDB3E4BA86A52557CFFA5D64B3654@atlmaiexcp01.iss.local>
- References: <632B4A260DDB3E4BA86A52557CFFA5D64B3654@atlmaiexcp01.iss.local>
- User-Agent: Opera7.02/Win32 M2 build 2668
Yes! Your hitting on an important point. I've seen management wave after
wave
come in to an organization and dictate to the "team" members what they are
going to do, how they are going to do it, and how they are going to like
it. XP or any other technique/method
is doomed to fail under these conditions. And when it fails, the managers
will crucify the method as another fad gone bad.
I keep this quote I found on the internet on my bulletin board to help me
remember how important building internal commitment is when implementing
change.
"I think that disciplined OO design and documentation is one of those
things that you can't legislate. A given group that's inclined to work in
an open way, documenting what it does, will just do that, tools or no
tools, and mandate or no mandate. And a group that's not inclined to work
that way just won't, period. "
Amen.
lee
On Thu, 13 Nov 2003 09:33:57 -0500, Fuqua, Andrew (ISSAtlanta)
<AFuqua@iss.net> wrote:
> XP is not an appropriate methodology...
> ... IF even 1 programmer on the team doesn't believe in it and isn't
> willing to suspend disbelief and really try to do it for at least a
> couple months. This is especially true if that programmer is keeping his
> feelings to himself, and even more so if he is being secretly subversive.
> If everyone is truly interested in continuous learning and SW development
> best practices and are genuinely trying to do XP (or scrum or any other
> flavor of Agile), I don't know of any inappropriate time.
> Of course, XP isn't always enough. For example, you'll want to break
> large teams into smaller XP projects and have something, probably SCRUM-
> ish, to tie them together. XP doesn't try to address all 10,000 things
> that have to be done to develop and ship a software product.
> Some may say the lack of management support would be an inappropriate
> time, but a strong or clever team-lead/coach can overcome even that
> problem.
> andrew m. fuqua
> president, xp-atlanta user group http://www.xp.thatatlantasite.com
> -----Original Message-----
> From: Gary Vecellio [mailto:vecellio@bellsouth.net]
> Sent: Monday, November 10, 2003 9:30 AM
> To: 'Atlanta Java Users Group'
> Subject: RE: eXtreme Programming
>
>
>
> Hi All:
>
>
>
> I'd be interested in people's insights and experiences related to a
> slightly different question. When would XP _not_ be an appropriate
> methodology?
>
>
>
> Thanks,
>
> Gary
>
>
>
>
--
Lee Chalupa
Something Else Enterprises, Inc.
lchalupa@seelink.org
770 381 2377