Re: Move from Tradition to XP - Jan 17th

On Friday, January 17, 2003, at 10:56:01 AM, Sandy wrote:

> Interesting little bit of feedback from one of the developers today. Their fear of
> adopting XP was that they had to jump through hoops to get management to grant them
> time to do detailed design documents. Now, they fear, they may lose that time. My job
> is to show them how they don't lose the time, but rather, make better use of it.

Why do they want to do detailed design documents? Why do they imagine that
doing XP would make them stop?

> I can certainly see the benefits of introducing TDD into a legacy organization,
> because it's the biggest bang-for-the-buck with respect to the QA effort. The effort
> I face is identifing all the loosely coupled components that lend themselves to
> unit-testing (the low-hanging fruit). And if I follow the belief of "don't refactor
> until the test is in place", then it gets tricky. 

Yes. The edge of the knife isn't at "don't refactor until the test is in
place" for legacy code. Unfortunately.

Ron Jeffries
www.XProgramming.com
He who will not apply new remedies must expect old evils.  -- Francis Bacon


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Turn flat surfaces into speakers with the Soundbug.
http://us.click.yahoo.com/QWAVSC/onCFAA/xGHJAA/nhFolB/TM
---------------------------------------------------------------------~->

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/