RE: Managing Extreme Programming

Ron,

> -----Original Message-----
> From: Ron Jeffries [mailto:[email protected]]

[>] snip
> 
> I want to gently suggest that this is a very bad idea. The value of a
> feature is generally unrelated to how hard it is to build. If the
> assumption were true, we wouldn't need the customer to order things in
> order of value, we'd order them in terms of largest cost first.

[>] Take the stories for the iteration, partition them on "testable
requirements boundaries," if the stories themselves don't do that
already. It may be two or more stories are needed to deliver a "testable
requirement."

Once these boundaries are defined, the partitioning of the value for the
iteration can take place. You are correct in not assigning value by the
difficulty.

> Now ... it turns out this is nearly the worst possible strategy if
value
> is
> randomly distributed over stories. The reason is that by doing the
> expensive stories first, we minimize the number of stories we do. And
if
> value is randomly distributed, we thus neatly minimize value as
> effectively
> as we can without knowing the actual values. Of value.
> 
> Ron 
[>]Glen B. Alleman


------------------------ 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/