Drupal code sprint formats
by Jacob Singh
I've been asked to facilitate a code sprint at Drupal Camp Delhi in a couple weeks. I've never led a code sprint before, but I have participated in several. I'm thrilled to do it, but then there are a lot of logistical questions that are rasied. What format it should take? Who and how many should attend? Will there be beer? These are serious questions that I don't have clear answers to. I thought about it and decided to describe the different formats I've witnessed.
General "grab an issue" sprint.
- Preparation: Low
- Easy to get involved: Yes, but tough for complete newbies unless there is prep.
- Tangible results: Low
- Group size: Any
Organized "grab an issue" sprint
- Preparation: Medium
- Easy to get involved: Yes because it is focused but the person shouldn't have to be an expert.
- Tangible results: Medium
- Group size: max 20 or so
Dedicated project w/ goals sprint
- Preparation: High
- Easy to get involved: No, people need to come with expertise.
- Tangible results: High
- Group size: small, maybe 8 people max for effective decision making
Do you have other formats which worked well? Why and in what scenarios?