Hi,
I would like to introduce the concept of sprinting to the MMBase community.
Okay, so what's a sprint?
In a nutshell a sprint is a multi-day session of intense development organized around extreme programming (XP) ideas such as pair programming.
In the zope/plone community sprints are a proofed development method and i think it can be very helpful for the MMBase community as well...
Usually a sprint has one or two specialized goals, such as wysiwyg, documentation, i18n, UI, getting a specific release done, bugfixing, things like that.
so what makes a sprint?
- a facilitator, somebody who takes the burden of organising it all (accomodation, food, drinks, travel plans, sleeping arragements, thins like that)
- one coach, the coach defines the agenda and makes sure the pairs are balanced
- Pairing, everybody should work in pairs, with at least one veteran per pair
- Every pair presents dayresults each evening
- Not too many people, about 8-10 is fine (4-5 pairs)
This way a lot of work can be done in just a few days, and/or people getting started devolping on MMbase can quickly get into the codebase by pairing up with an experienced MMBase developer.
more information about (Zope/Plone) sprints can be found at:
http://www.zopemag.com/Guides/miniGuide_ZopeSprinting.html http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/SprintSchedule http://plone.org/events/sprints/whatis
Now, I would like to use this mail thread to elaborate on the usage of sprints in MMBase developing :)
greetings,
Willem Voogd
