[bind10-dev] Working style for the next sprint

[Shane Kerr]

All,

We are beginning our next sprint. I would like to take the opportunity
to see if we can improve our working style.


The folks from CNNIC have suggested that it might make sense to try to
erase some of the boundaries between the ISC team and the rest of the
team. To do this, we may try to have more than one person working on a
ticket at the same time. I'm not sure of the best way to do that, so if
you can please think about it and come up with a way to share work on a
deliverable that would be cool.

Perhaps this could be something as simple as splitting deliverables up
into multiple tickets and then having one person review the other
person's work?


Also, I know we had a bit of a crunch at the last release. I think this
is not necessarily avoidable - deadlines cause people to work harder. I
don't think planning could have made things much better. It's not
pretty, and I know it's not so nice for Jeremy (or the rest of you guys
who were up past midnight working on the code), but I don't think there
is much we can do to avoid it. Shorter deadlines means we divide the
chaos up into smaller bits, but there is still chaos.

Having said that, I am open to suggestions on how to avoid this. Perhaps
better estimates will help, although I am not optimistic. Perhaps having
even shorter release cycles will help. We can try for 2x 3-week sprintgs
instead of the one 6-week sprint for the next iteration, for example.


Finally, some semi-nagging... do we think that the bind10-daily-status
is useful any more? I confess I haven't updated in weeks, but I also
admit that I do check to see what other people are up to. If we think
it's useful, then perhaps just a commitment to use it is enough (and
some nagging from me). :)


Anyway, keep up the good work guys. Progress is being made! BIND 10
improves daily!

--
Shane