Re: 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


--- In [email protected], "Kent Beck" <kent@t...> wrote:
> I'm voting for ~20 days for release 0.1 (5 May to 29 May) and ~30 for
> release 0.2. 
>  
> You'll note I always write "SIP ~ N", trying emphasize that the actual
> number is less important than the trend.
>  
> I'm tempted to treat you-and-your-customer as a single team and measure
> SIP for both of you together. Perhaps I would wait on that, though
> because they are paying you regularly. If they can't learn to absorb
> value faster, though, much of your productivity/quality/flexibility
> advantage won't be able to play.
>  
> Kent 
> 
> -----Original Message-----
> From:
> sentto-8007113-447-1055947907-kent=threeriversinstitute.org@r...
> ps.yahoo.com
> [mailto:sentto-8007113-447-1055947907-kent=threeriversinstitute.org@retu
> rns.groups.yahoo.com] On Behalf Of pgbossi
> Sent: Wednesday, June 18, 2003 7:50 AM
> To: [email protected]
> Subject: [SIP] How to measure SIP?
> 
> 
> Historically:
> *) Tue 25/02/03 ==> first meeting with the customer
> *) Fri 11/04/03 ==> deploy in pre-production what he has called
> release 0.0; customer validates our work and gives permission for
> payments
> *) during April the customer was almost "sleeping" for his own
> organization internal issues
> *) Mon 05/05/03 ==> new features from the customer that will
> constitute release 0.1 and release 0.2
> *) Wed 14/05/03 ==> deploy in production of release 0.0, but really
> never officially launched to end users by the customer (organizational
> issues again)
> *) Wed 21/05/03 ==> deploy in production of release 0.1
> *) Thu 29/05/03 ==> official launch to the end users of release 0.1
> *) Mon 09/06/03 ==> deploy in pre-production of release 0.2; customer
> validates our work and gives permission for payments again
> 
> We are currently waiting to deploy in production release 0.2, but no
> more functionalities were added since Mon 09/06/03 and all the
> requested features have been implemented. Apparently the customer
> continuously has these idle times that affect our rhythm.
> 
> Ok, if you are still awake I can show you some measures. All the
> scenarios that I'm presenting here include customer sleep during
> April.
> 
> SIP=93 days
> This is the value that we get if we count only features that are
> currently in use by end users and if we consider that roughly
> everything was already at least mentioned during the first meeting
> (but not detailed).
> 
> SIP=39 days
> This value is calculated considering releases 0.0 and 0.1 only, taking
> into account as delivery dates Fri 11/04/03 for release 0.0 stories
> and Thu 29/05/03 for release 0.1
> 
> SIP=35 days
> We get this value if we include release 0.2 into the above and if we
> consider delivery date Mon 09/06/03 for release 0.2 stories
> 
> SIP=22 days
> Like the "35 days" case, but considering as the starting date of each
> user story the day in which the user story was really planned (every
> iteration was defined in a planning game session, every iteration
> lasted for about 1 week).
> 
> SIP=19 days
> A slight modification of the "22 days" case: the starting date of each
> user story is the first day in which the user story has been actually
> worked. This is suggested in SIP paper too, because "the details are
> specified when a programmer has a conversation with a customer just
> before programming".
> 
> I think that the "19 days" case is a little bit too stretched, because
> this particular customer was not on-site every day, sometimes there
> were phone conversations, maybe in other occasions the developer
> started working with less details, asking questions to the customer
> the day after. In any case, I hope that it gives an idea of the
> different possible ways in order to measure SIP.
> 
> So, what do you think? Which is the most appropriate way to calculate
> SIP?
> 
> Cheers, Giuliano
> 
> 
> 
> Yahoo! Groups Sponsor	
>  
> <http://rd.yahoo.com/M=251812.3170658.4537139.1261774/D=egroupweb/S=1705
> 007181:HM/A=1564415/R=0/SIG=11t6t7kdo/*http://www.netflix.com/Default?mq
> so=60164784&partid=3170658> 	
>  
> <http://us.adserver.yahoo.com/l?M=251812.3170658.4537139.1261774/D=egrou
> pmail/S=:HM/A=1564415/rand=273616938> 	
> 
> To unsubscribe from this group, send an email to:
> [email protected]
> 
> 
> 
> Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service
> <http://docs.yahoo.com/info/terms/> .


------------------------ Yahoo! Groups Sponsor ---------------------~-->
Looking for the latest Free IT White Papers?
Visit SearchSecurity.com to access over 500 white papers.
Get instant access at SearchSecurity.com Today
http://us.click.yahoo.com/ayjvfD/QLNGAA/uitMAA/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/