[bind10-dev] Method of estimating (was: Re: [sprint planning] estimates for sprint ending 2012-10-23)

Jelte Jansen jelte at isc.org
Tue Oct 9 12:02:11 UTC 2012


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 10/09/2012 10:18 AM, Michal 'vorner' Vaner wrote:
> 
> Anyway, I think what we did is allowing the averages to have any
> value, not the estimates (so if there's 3 and 5, we can average to
> 4).
> 

That was the original approach, but I have never really enforced this,
and over time some of us (including me) got more loose with the
numbers we submitted. And some may even never have realized it at all :)

So yeah, let's try to use these numbers as what we submit from next
sprint.

But I have a bigger change in mind, and would also like to propose an
experiment for next sprint. this is probably also something we want to
discuss at next week's bi-weekly call.

Not fully formed yet (esp. since some other regular dates will need to
change and I have not talked about this to anyone yet), but in general
I want to create the opportunity to actually discuss estimates we seem
to disagree about.

Instead of collecting the estimates over the weekend and doing them on
monday, I want to try the following schedule:

- - Have pre-sprint-planning (i.e. my talk with product owner and
manager) collect unestimated tickets, and send out estimate requests
on *thursday*.
- - Have everyone do the estimates on friday
- - I will collect them, and make a list of tickets where the estimate
appears to warrant discussion (either on friday or first thing on monday)
- - Monday is then the day to discuss them
- - final decision on the estimates is done on tuesday (for now, by me;
in this current proposal I do not propose to do a full second round,
but this may change).

This has the drawback that we need which tickets to estimate even
earlier, but I am hoping that will be offset by us all having a better
view of what the amount of work for any ticket is.

So I propose that we discuss this next week, try it for next sprint,
and discuss it again in 3 weeks time.

Jelte
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://www.enigmail.net/

iEYEARECAAYFAlB0EkMACgkQ4nZCKsdOncUtowCg1WCP3aNYD9Lz4MJmJhHVCUTg
pxoAniltpA9dNLD88d5ihoGvgh1jAmzD
=ajsq
-----END PGP SIGNATURE-----


More information about the bind10-dev mailing list