RE: How to measure SIP?

"Kent Beck" <[email protected]> Thu, 19 Jun 2003 09:20:52 -0700
Newsgroups gmane.comp.programming.software-in-process
Organization Three Rivers Institute
Message-ID <001b01c3367e$c25d75f0$0401000a@KentsT30>
I "only" have an aesthetic/intellectual argument for when to start the
SIP clock, not any experience. You have some capital to invest. At some
point, you start applying it towards a particular feature, so you can't
apply towards any other feature (opportunity cost). At some future
point, you receive revenue, so you have capital again. Symmetry suggests
to me that we should start measuring when the capital becomes
unavailable and stop measuring when it becomes available again. This
suggests B to me, since writing a story on a card doesn't really prevent
me from writing 100 other stories on other cards.
 
Does that answer your question?
 
Kent

-----Original Message-----
From:
sentto-8007113-449-1056007899-kent=threeriversinstitute.org@returns.grou
ps.yahoo.com
[mailto:sentto-8007113-449-1056007899-kent=threeriversinstitute.org@retu
rns.groups.yahoo.com] On Behalf Of pgbossi
Sent: Thursday, June 19, 2003 12:32 AM
To: [email protected]
Subject: Re: [SIP] How to measure SIP?


Kent, thanks for your answers. I'd like to have a few more
clarifications.

First of all, you don't want to consider release 0.0 because it has
never been used by end users, do you? I'd agree with you, but there's
another element to consider: release 0.0 goal was more to show results
to customer's upper management than to really go in production. In
this way, wouldn't be appropriate to measure SIP(0.0) ~ 40 days?

I like the idea to trace SIP release after release and not necessarily
as an overall value, it gives much more a sense of what's happening as
time goes by.

Which is the most appropriate way to consider the starting date of a
user story?
A) when the story is written down on a card
B) when the story is planned
C) when the developers start working on the story

I'd vote for B, because we are trying to ask the customer to write
acceptance tests right after the planning game: by specifying the
acceptance tests a lot of details behind the user story are written at
least narratively (we are shifting the customer towards FIT, but this
is an entirely different story).

Ciao, Giuliano