Re: Managing Extreme Programming

On Monday, January 13, 2003, at 2:48:08 PM, Laurent Bossavit wrote:

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

Yes, but the OP's suggestion was that cost == value, and therefore the sort
would be done on cost, not on real value. Recall:

On Monday, January 13, 2003, at 11:30:26 AM, Dinwiddie, George wrote:

> At the start of the project, you have a bunch of user stories, or some other
> description of what the project intends to build.  You have some idea of the
> value of this work.  Because the value of this work is likely to be very
> difficult to determine via objective means,
<emphasis>
> you're very likely to use the
> simplifying assumption that it's worth what it takes to produce it--
</emphasis>
> else we
> wouldn't be doing it.  So, Budgeted Cost of Work Scheduled (BCWS) is assumed
> to be the value of the completed work.

Ron Jeffries
www.XProgramming.com
"How do I get to XP?"  "Practice, man, practice."


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