PyConDC 2004 Sprint plan

What is a sprint?

A sprint is a focused development session, in which developers pair in a room and focus on building a particular subsystem. A sprint is organized with a coach leading the session. The coach sets the agenda, tracks activities, and keeps the development moving. The developers work in pairs using XP's pair programming approach.

The sprint approach works best when the first few hours are spent getting oriented -- presenting a tutorial for the development material, laying out the stories to tackle for the day, getting everyone a CVS checkout to work with.

ZopeMag's miniGuide to Zope Sprinting is a good introductory article; just mentally remove every "Zope" from the article to make it generic.

Why sprint at PyCon?

The sprints are intended to benefit the Python core, and to encourage more developers to take part in Python's development. They will also be a good place to see ExtremeProgramming or other AgileMethods in action, and to work closely with experienced Python developers. What would you like to see done, or at least attempted?

PyCon will always have a core Python sprint. Other topics will come and go each year.

If you wish to participate in a sprint, please contact the sprint organizers in advance! Sprint topics are listed below.

Sprints Being Planned for PyConDC2004

Brief summaries of and links to approved sprints should go here.

Proposed Sprint Topics

Here are several topics that have been proposed but not yet accepted. If you think this would be a good sprint topic, add a comment in the wiki or send a comment to Jeremy Hylton. In some cases, the topic has been assigned but the coach hasn't. Feel free to volunteer to coach one of these sprints.

Other ideas:

Willing Participants Without a Particular Sprint Yet

Logistics

Who makes this possible?

The Python Software Foundation is sponsoring the sprints for PyConDC2004. Please consider making a donation to support this vital community activity!

PyConDC2004/SprintPlan (last edited 2008-11-15 14:01:09 by localhost)

Unable to edit the page? See the FrontPage for instructions.