RE: Re: Managing Extreme Programming

Yep and what's missing is BCWS. Also the "average" approach is replaced
by the "actual" BCWP.

Dollarizing velocity is done in the way you described; as well the SV is
the additional outcome. With those EAC can be computed. 

Now keep all those values in the DB for all cycles, and build the EAC
model. The simple approach is 

EAC = Cost to Date + Estimated Cost of Remaining Work.

But there are dozens of others. We use back weighted cumulative CPI/SPI,
plus some "adjustments" for reporting accuracy etc.

Glen B. Alleman 

> -----Original Message-----
> From: [email protected] [mailto:[email protected]]
> Sent: Friday, January 10, 2003 12:16 PM
> To: [email protected]
> Subject: [xpAdoption] Re: Managing Extreme Programming
> 
> Hi Glen,
> 
> > > > (6.1) How to dollarize the velocity units in terms the project
> > > > accounting folks will accept.
> > >
> > > Lets see...  If x developers average y units per iteration, and
> > > the fully-loaded cost of those x developers is $z per iteration,
> > > then the cost per velocity unit is $z/y.  Not so difficult.
> >
> > [>] Except this calculation I a level of effort and does not
> > describe the "value" in dollars of the delivered code.
> 
> In George's example, y is the Budgeted Cost of Work Performed (BCWP),
> and z is the Actual Cost of Work Performed (ACWP).  So George's
> cost-per-velocity-unit is ACWP/BCWP, the reciprocal of Cost
> Performance Index (CPI).  If you can dollarize CPI, you can dollarize
> velocity.
> 
> Dale 


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