Distributed Pair Programming
•Transferir como PPTX, PDF•
1 gostou•952 visualizações
Are two heads better than one? Isn't that twice as expensive? No, pairing goes almost twice as fast, but saves costly errors later. I can be done face to face or remote, and works for non software projects as well.
Recomendados
Recomendados
Mais conteúdo relacionado
Destaque
Destaque (17)
Semelhante a Distributed Pair Programming
Semelhante a Distributed Pair Programming (20)
Mais de Agile Dimensions LLC
Mais de Agile Dimensions LLC (19)
Último
Último (20)
Distributed Pair Programming
- 1. AgileBill Krebs UNM, UWA Distributed Pairing IBM, ASPE Allscripts Dev 82 Agile 01 CSM, CSP MBTI, CVW IGTF, IGQI The Distributed Agile Series Coaching distributed teams since 2009 Copyright © 2012 Agile Dimensions LLC
- 2. Is this your team? Test Dev PM BA Allscripts Agile Academy
- 3. Do Daily Meet Dev CI-Build [ Pair, UT, Refactor ] Test ( Refine ) Allscripts Agile Academy
- 4. Pairing • Two people, one computer. Switch • Save ½ the bugs for +15% labor • Best benefits are intangible Allscripts Agile Academy
- 5. Microsoft Research • “Pair Programming – What’s in it for me” Andrew Begel, Nachiappan Nagappan , Microsoft Research http://research.microsoft.com/pubs/75108/esem-begel-2008.pdf Pair programming is a practice in which two programmers work collaboratively at one computer on the same design, algorithm, or code. Prior research on pair programming has primarily focused on its evaluation in academic settings. There has been limited evidence on the use, problems and benefits, partner selection, and the general perceptions towards pair programming in industrial settings. In this paper we report on a longitudinal evaluation of pair programming at Microsoft Corporation. We find from the results of a survey sent to a randomly selected 10% of engineers at Microsoft that 22% pair program or have pair programmed in the past. Using qualitative analysis, we performed a large-scale card sort to group the various benefits and problems of pair programming. The biggest perceived benefits of pair programming were the introduction of fewer bugs, spreading code understanding, and producing overall higher quality code. The top problems were cost-efficiency, (work time) scheduling problems, and personality conflicts. Most engineers preferred a partner who had complementary skills to their own, who was flexible and had good communication skills. Allscripts Agile Academy
- 6. Top 10 Benefits (%) 66 Fewer Bugs 42 Spreads Code Understanding 48 Higher Quality Code 42 Can Learn from Partner 30 Better Design 22 Constant Code Reviews 22 Two Heads are Better than One 17 Creativity and Brainstorming 14 Better Testing and Debugging 13 Improved Morale Allscripts Agile Academy
- 7. Formal Inspection • Different styles • Save ½ the bugs for +15% labor • Does it fit in a 3 day story? Allscripts Agile Academy
- 8. $$ Series 1 Cost of change 100 90 Place these: 80 Unit Test 70 Build 60 QA bug 50 40 Pairing 30 20 Customer bug 10 0 Inspection a b c d e f g hTime -> j i Allscripts Agile Academy
Notas do Editor
- Table of ContentsPair programming is a practice in which two programmers work collaboratively at one computer on the same design, algorithm, or code. Prior research on pair programming has primarily focused on its evaluation in academic settings. There has been limited evidence on the use, problems and benefits, partner selection, and the general perceptions towards pair programming in industrial settings. In this paper we report on a longitudinal evaluation of pair programming at Microsoft Corporation. We find from the results of a survey sent to a randomly selected 10% of engineers at Microsoft that 22% pair program or have pair programmed in the past. Using qualitative analysis, we performed a large-scale card sort to group the various benefits and problems of pair programming. The biggest perceived benefits of pair programming were the introduction of fewer bugs, spreading code understanding, and producing overall higher quality code. The top problems were cost-efficiency, (work time) scheduling problems, and personality conflicts. Most engineers preferred a partner who had complementary skills to their own, who was flexible and had good communication skills.
- for (int I = 0; i<10; i++); { // do stuff}