I like the idea of a hybrid model - namely, every planned feature & task goes into JIRA, but we choose and tag a set of primary & secondary tasks for the current sprint. The idea is to encourage developers to choose and assign to themselves primary tasks where possible, and secondary tasks otherwise. Keeping a regular sprint schedule gives a nice pace & rhythm to the project, and the looming end of a sprint can often be a spur to find a bit of extra time to complete a task - I think this helps to keep the momentum of the project going, especially since we have a very small community at this stage.
Cheers, Darren >Hi Robert, > >On Mon, Feb 9, 2009 at 9:49 AM, Robert Burrell Donkin ><[email protected]> wrote: >> ...in the the spirit of http://c2.com/cgi/wiki?WhyWikiWorks and >> http://c2.com/cgi/wiki?WhyWikiWorksNot, i'd like to jump in and add a >> counter-point not because i disagree with Bertrand but i am interested >> in seeing whether sprints could work within a collaborative open >> development environment... > >Thanks for this - I do agree with your point of view, and also that >the (sacred?) Apache way of doing things should not stay cast in stone >forever. > >Any other opinions on this? > >-Bertrand -- [email protected]
