Re: Responsibility

Hi Ron,

> Here's a question: consider a project that assigns a dollar value to
> each story, and another project that only knows, for any pair of
> stories, which one is worth more.
>
> What differences could we detect in the decisions made in these two
> projects?

If the team knows the cost of an iteration, the dollar value project
can decide whether the next iteration is worth the cost.  If so, do
it.  If not, stop and call the project done (until some more valuable
stories come in).

The dollar value project wouldn't have to justify its existence to its
customer.  The customer would know what value the project has created.
 I don't know whether XP teams often have to justify their existence,
but I've been through the "So, tell me again what I'm paying you for"
process too many times.  And I've heard "IT costs too much" too many
times.

The dollar value team members would know an important part of the
value they create for the company.  (There are also other kinds of
value besides money.  Don't know how to tally those.)  I would find
that motivating.  I don't know exactly how that would inform my decisions.

Knowing the value of each story could also raise some sticky issues. 
"We created $XXX value for you in the last year, and you're paying us
only $YYY."

Dale



------------------------ Yahoo! Groups Sponsor ---------------------~-->
Get 128 Bit SSL Encryption!
http://us.click.yahoo.com/CBxunD/vN2EAA/xGHJAA/NhFolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, send an email to:
extremecustomering-unsubscribe-hHKSG33TihhbjbujkaE4pw@public.gmane.org

 

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/