[bind10-dev] Sprint task list and estimates

Jelte Jansen jelte at isc.org
Wed Jun 1 12:33:09 UTC 2011


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

On 06/01/2011 01:57 PM, Shane Kerr wrote:
> Stephen,
> 
> On Tue, 2011-05-31 at 19:22 +0100, Stephen Morris wrote:
>> One thing we didn't discuss is what to do with the tickets left in the
>> "Next-Sprint-Proposed" milestone.  As we have discussed them and have
>> not included them, should these go into the general pool/year 3 backlog?
>>  Or are they sufficiently important that we should keep them in that
>> milestone.
> 
> I'm thinking we should move them all out of the list and into the Year3
> backlog. Otherwise we risk having this be just another holding cell for
> tickets.
> 

umz, not sure actually. Maybe we want to discuss this per ticket as well during
the sprint planning meeting, since it kind of depends on the reason they weren't
included.

If it is only because the next sprint was 'full', as it were, then the reason
for proposing it go into the next hasn't changed, and we're just bouncing
tickets (i know i'll propose the ones i did for next sprint again).

If it is because we decide the task can wait, then it could (perhaps) go back on
the backlog

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

iEYEARECAAYFAk3mMYUACgkQ4nZCKsdOncViRQCg14s7mDKEK1LsFk2F94ie3Rh0
5HAAn1rW8LlX65uJj1GCnAsz+RnvU3lq
=mLNy
-----END PGP SIGNATURE-----



More information about the bind10-dev mailing list