RE: Managing Extreme Programming

Yep,

> -----Original Message-----
> From: Arien Malec 
> 
> My understanding is that EV assumes that if you say you are 80% done
> with a task, you have generated 80% of the value of that task. Glen,
> on my understanding, is changing that to an all or nothing generation
> of value, based on the passing of customer tests.
> 
> E.g., if the BCWS was $1000 for story X, and the programmer thought
> story X was 80% of the way done, classic EV would allow a BCWP of
$800,
> but Glen would only allow two values: 0, if the tests don't pass, and
> $1000, if they do pass.

[>] in the old EV method partial completion produced partial credit.
This works for pouring concrete and we use it for just that (installing
a Nextel system here), but for software its all or nothing. 

That's an easy concept but if the granularity is too large the "oops" is
also too large. If the "value booking increments" are small (fine
grained) then the incremental accumulation of value represents the
"physical" progress of the project as well. 

The gap in most progress measurement systems is the disconnect between
"percent complete" and "physical percent complete." In fact until MSFT
Project 2002 professional there was no representation of physical
percent complete. 

XP's way of measure progress and percent complete is "physical" percent
complete == wa la we're home free with EV.

> Thus Glen is changing a continuous or analog measurement of value
> into a discrete, or digitial measurement of value.
> 
> Do I have that right, Glen?

[>] You're there. 

> Arien 

[>] Glen


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