RE: Managing Extreme Programming

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

Yes, but I'm suggesting that
 - only for calculating these project-wide summary numbers
 - only when you don't have a better means of estimating the $ value of the
project
 - and only because this seems to be the standard practice.

I'm not suggesting that the stories be prioritized based on this value.  As
I see the matter at hand, the goal is for the development team and/or
low-level managers to be able to report the results of an XP project to
upper management in a manner to which they've become accustomed and which
insulates them from the details, making project to project comparisons
easier.  As a side benefit, if done well, the numbers which are reported are
better grounded in reality and less dependent on optimism.

From the other side, the goal is to enable the better steering that XP
provides while still monitoring the progress in their customary accounting
terms.  This gives the benefit that, when the analysis shows a problem,
there are options besides the binary "continue"/"cancel" decision.

 - George

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Flexible Keyboard is the ideal accessory for PDA users that are on the move.
http://us.click.yahoo.com/dCBVZC/WnCFAA/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/