[pypy-svn] r20500 - pypy/extradoc/talk/22c3
bea at codespeak.net
bea at codespeak.net
Thu Dec 1 15:36:16 CET 2005
Date: Thu Dec 1 15:36:15 2005
New Revision: 20500
inserting and modifying text on sprinting - more on how it was changed later in the text
--- pypy/extradoc/talk/22c3/agility_v1.txt.txt (original)
+++ pypy/extradoc/talk/22c3/agility_v1.txt.txt Thu Dec 1 15:36:15 2005
@@ -17,10 +17,27 @@
+Agile approaches: sprinting
+The first drafts of ideas of what was to become PyPy started during a sprint, held in Hildesheim in February 2003. Inspired by this practice, used by other Python oriented projects such as Zope. Originally the sprint methodology used in the Python community grew from practices within Zope Corporation. Their definition of a sprint is "two-day or three-day focused development session, in which developers pair off together
+in a room and focus on building a particular subsystem".
+It was decided early that sprinting was to be the key technique in creating a collaborative and open community. The early PyPy sprints moved around, being organised by core developers together with local Pythonistas and soon to become PyPy:ers in LOvain Le Neuve, Gothenburg,Vilnius and Amsterdam.This strategy helped to create as well as strengthen the growing community and sprints gave the opportunity to both help, participate and influence the idea of PyPy.
+Sprints as such is not part of the Agile portfolio of techniques, the closes thing to it comes from Scrum who names the 30 days long programming iterations "sprints", covering a certain increment. In the Scrum method considerable effort is placed into performing the sprint planning as well as creating and documenting the "sprint backlog" which is then feedbacked into the "Product backlog".The sprint ends with a "sprint review" - an informal planning session in which the team decides on upcoming work, there are also techniques in which the team looks at ways to improve the development methodology and future sprints.
+The practise used within the Python community and by Zope Corporation is an adoption of just this aspect of Scrum - not the entire Scrum methodology which covers more than just sprinting. Here - and even in the early days of PyPy sprints where limited to 2-3 days, which in some sense reduces the need for rigourous planning beforehand but also the need to review the process. We will come back to this subject later on.
+Why did PyPy choose sprinting as a key technique? It is a method that fits distributed teams well because it gets the team focused around clear (and challenging) goals while working collarobative (pairprogramming, status meeting, discussions etc) as well as accelerated (short increments and tasks, "doing" and testing instead of long start ups of planning and requirement gathering). This means that most of the time a sprint
+is a great way of getting results, but also to get new people aquinted with
+the codebase. It is also a great method for dissemination and learning within
+the team because of the pairprogramming.
+Agile approaches: testdriven development
-- testdriven development
- transparent communication
More information about the Pypy-commit