logo       

RE: Practice: Weekly Cycle: msg#00020

programming.extreme-programming.xp-explained2

Subject: RE: Practice: Weekly Cycle




> -----Original Message-----
> From: Ron Jeffries
[mailto:ronjeffries-iH4XQsbo15BDlFalPvvQyA@xxxxxxxxxxxxxxxx]
...
> I believe that for all practical purposes, there are no technical
> dependencies between stories. After two stories are programmed, there may
> be opportunities for refactoring. And a team that is in full communication
> sees these coming, and starts the refactoring early.

Hi Ron,

I don't quite understand. What do you mean by "early"?
Not before there is duplication, I hope. And I imagine
not before the bar is Green.

You seem to be saying that dependencies between stories
are really just "preemptive refactorings" in the minds of
the developers. And, if you just except the fact that
you *may* need refactoring afterwards, then you can keep
the stories independent. I agree.

But, suggesting that a team "starts the refactoring early"
doesn't sound much different then the preemptive mental
refactorings that lead to the belief in story dependencies.
I have to admit that I often fall prey to this - denying
there is any real dependency between the stories, but then
being very careful to pick the right one first...

Could you explain this a bit more? Thanks.

-- Jim Long



------------------------ Yahoo! Groups Sponsor --------------------~-->
$4.98 domain names from Yahoo!. Register anything.
http://us.click.yahoo.com/Q7_YsB/neXJAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~->




<Prev in Thread] Current Thread [Next in Thread>
Google Custom Search

News | FAQ | advertise