In attesa di ricevere qui feedback anche su cosa/quando la collaborazione non è efficace, economica od efficente mi segno alcune annotazioni sul Pair Programming:
- Two programmers working side-by-side, collaborating on the same design, algorithm, code or test.
- One programmer, the driver, has control of the keyboard/mouse and actively implements the program. Types and thinks tactically about the method being created.
- The other programmer, the observer, continuously observes the work of the driver to identify tactical (syntactic, spelling, etc.) defects and also thinks strategically about the direction of the work.
- On demand, the two programmers can brainstorm any challenging problem.
- The two programmers periodically switch (30min) roles, they work together as equals to develop software.
- 2 people working at a single computer will add as much functionality as two working separately except that it will be much higher in quality (da verificare se è vero ed in che condizioni)
Le fonti: http://www.pairprogramming.com/ , http://www.extremeprogramming.org/rules/pair.html
Update 24-02-2006:
Pair programming is a dialog between two people trying to simultaneosly program and understand how to program better (Kent Beck)
Tags :
Team Work |
Agile |
Pratiche |