Re: Managing Extreme Programming

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

Not that I'm disagreeing or anything, but it seems to me that *if* 
stories are sorted in descending order of value, *then* you can make 
the assumption that each one is worth (at least) what it costs to 
build; this because the Customer will have known the cost of the 
stories when prioritizing them. If a story costing three points was 
not *at least* three times as valuable as one costing one point, it 
wouldn't have been scheduled first.

Cheers,

-[Morendil]-
Adding manpower to a late project makes it later. -- Fred Brooks



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