--- In extremeprogramming <at> yahoogroups.com, "banshee858"
<cnett858 <at> h...> wrote:
> Why do I think refactoring costs?  Because time-and-time again teams,
> or individuals, talk about the need for a "refactoring iteration" and
> how to explain that to the boss.  Why do they need to spend an
> iteration producing nothing of value to the customer?  Because they
> have so packed each and every iteration with user stories, there was
> no slack for refactoring, i.e. improving the design.  In effect, they
> ignored the cost of refactoring in favor of new features.

So there are several aspects to this: the opportunity cost of doing
the refactoring (wich comes now) vs the penalty for not having done
the refactoring (which comes later). No surprise that folks are
tempted to put off refactoring. Meanwhile, there's also the _actual_
cost of doing the refactoring, which in the XP case is nothing more
than a cost of doing business. But one which it is easy for a manager
to think that they can deem to be zero for an iteration with no severe
penalty. 

I wonder if the message from the community is quite clear and explicit
on all of these, not least because of the time-and-again phenomenon
mentioned above.

Keith

To Post a message, send it to:   extremeprogramming <at> eGroups.com

To Unsubscribe, send a blank message to: extremeprogramming-unsubscribe <at> eGroups.com

ad-free courtesy of objectmentor.com