[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-1-en-105":3,"doc-seo-359764-105":53,"doc-detail-359764-en":126},{"code":4,"msg":5,"data":6},0,"success",[7,14,19,24,29,34,39,44,49],{"id":8,"doc_module":9,"doc_module_name":10,"category_name":11,"show_sort_weight":12,"slug":13},11,1,"Template","Presentations",90,"presentations",{"id":15,"doc_module":9,"doc_module_name":10,"category_name":16,"show_sort_weight":17,"slug":18},12,"Resumes",80,"resumes",{"id":20,"doc_module":9,"doc_module_name":10,"category_name":21,"show_sort_weight":22,"slug":23},14,"Invoices",70,"invoices",{"id":25,"doc_module":9,"doc_module_name":10,"category_name":26,"show_sort_weight":27,"slug":28},15,"Posters",60,"posters",{"id":30,"doc_module":9,"doc_module_name":10,"category_name":31,"show_sort_weight":32,"slug":33},16,"Social Media",50,"social-media",{"id":35,"doc_module":9,"doc_module_name":10,"category_name":36,"show_sort_weight":37,"slug":38},17,"Forms",40,"forms",{"id":40,"doc_module":9,"doc_module_name":10,"category_name":41,"show_sort_weight":42,"slug":43},18,"Letters",30,"letters",{"id":45,"doc_module":9,"doc_module_name":10,"category_name":46,"show_sort_weight":47,"slug":48},21,"Paper Templates",5,"papers-templates",{"id":50,"doc_module":9,"doc_module_name":10,"category_name":51,"show_sort_weight":4,"slug":52},158,"General","general-158",{"code":4,"msg":54,"data":55},"ok",{"site_id":56,"language":57,"slug":58,"title":59,"keywords":60,"description":61,"schema_data":62,"social_meta":119,"head_meta":121,"extra_data":123,"updated_unix":125},105,"en","effects-of-pair-programming-at-the-development-team-level-an-experiment","Effects of Pair Programming at the Development Team Level - An Experiment","","Pair programming is studied for its effects at the development team level, focusing on productivity, defect counts, design quality, knowledge transfer, enjoyment, and effort estimation accuracy. The research uses an experiment with five four-person teams executing 400-hour projects under the same specifications, technologies, and process guidelines, differing only in using pair programming for all development versus using solo programming. Results show reduced early-case effort, no later differences, mixed productivity and testing outcomes, and improved knowledge transfer.",{"@graph":63,"@context":118},[64,80,101],{"@type":65,"itemListElement":66},"BreadcrumbList",[67,71,74,77],{"item":68,"name":69,"@type":70,"position":9},"https://docshare.wps.com","Home","ListItem",{"item":72,"name":10,"@type":70,"position":73},"https://docshare.wps.com/template/",2,{"item":75,"name":46,"@type":70,"position":76},"https://docshare.wps.com/template/paper-templates/",3,{"item":78,"name":59,"@type":70,"position":79},"https://docshare.wps.com/template/effects-of-pair-programming-at-the-development-team-level-an-experiment/359764/",4,{"url":78,"name":59,"@type":81,"image":82,"author":87,"headline":59,"publisher":90,"fileFormat":93,"inLanguage":57,"description":61,"dateModified":94,"datePublished":95,"encodingFormat":93,"isAccessibleForFree":96,"interactionStatistic":97},"DigitalDocument",{"url":83,"@type":84,"width":85,"height":86},"https://docshare.wps.com/thumbnails/effects-of-pair-programming-at-the-development-team-level-an-experiment/359764.png","ImageObject",442,249,{"name":88,"@type":89},"Connor ","Person",{"url":68,"name":91,"@type":92},"DocShare","Organization","application/pdf","2026-10-11","2026-09-23",true,{"@type":98,"interactionType":99,"userInteractionCount":73},"InteractionCounter",{"@type":100},"ViewAction",{"@type":102,"mainEntity":103},"FAQPage",[104,110,114],{"name":105,"@type":106,"acceptedAnswer":107},"How was the experiment set up to compare pair programming and solo programming?","Question",{"text":108,"@type":109},"Five four-person teams completed 400-hour projects using the same specifications, technologies, and process guidelines. Three teams used pair programming for all development work, while the other teams used solo programming.","Answer",{"name":111,"@type":106,"acceptedAnswer":112},"Did pair programming always improve productivity and effort estimation?",{"text":113,"@type":109},"Pair programming increased development effort for the first few use cases, but later use case efforts were almost the same as with solo programming. Effort estimation was slightly better early on for externally specified use cases, but solo programmers were more accurate when updating estimates right before implementation.",{"name":115,"@type":106,"acceptedAnswer":116},"What effects did pair programming have on defects and knowledge transfer?",{"text":117,"@type":109},"Pair programming teams had less pre-delivery but more post-delivery defects. Knowledge transfer improved in both breadth and depth, as code packages were understood well by more developers than in the solo programming teams.","https://schema.org",{"og:url":78,"og:type":120,"og:title":59,"og:site_name":91,"og:description":61},"article",{"robots":122,"canonical":78},"index,follow",{"doc_id":124,"site_id":56},359764,1791695709,{"code":4,"msg":5,"data":127},{"doc_id":124,"user_id":128,"nickname":88,"user_avatar":129,"doc_module":9,"category_id":45,"category_name":46,"doc_title":59,"doc_description":61,"doc_content":130,"file_id":131,"file_url":132,"file_type":133,"file_size":134,"view_count":73,"is_deleted":4,"is_public":9,"is_downloadable":9,"audit_status":9,"page_count":135,"language":136,"language_code":57,"site_id":56,"html_lang":57,"table_of_contents":60,"faqs":137,"seo_title":138,"seo_description":61,"update_tm":139,"read_time":140},687207022233,"https://ap-avatar.wpscdn.com/davatar_155a257f0dc6eb9ab79c44ca47cae57d","HELSINKI UNIVERSITY OF TECHNOLOGY Department of Computer Science and Engineering  \nJARI VANHANEN  \nEffects of Pair Programming at the Development Team Level: An Experiment  \nLicentiate thesis submitted for official examination for the degree of Licentiate in Technology.  \nEspoo, 27.05.2005  \nInstructor: Casper Lassenius  \nSupervisor: Casper Lassenius  \n\n| HELSINKI UNIVERSITY OF TECHNOLOGY\u003Cbr>Department of Computer Science and Engineering | ABSTRACT OF LICENTIATE THESIS |  |\n| --- | --- | --- |\n| Author\u003Cbr>Jari Vanhanen |  | Date\u003Cbr>27.05.2005 |\n|  |  | Pages\u003Cbr>48 |\n| Title of thesis\u003Cbr>Effects of Pair Programming at the Development Team Level: An Experiment |  |  |\n| Professorship\u003Cbr>Software Engineering |  | Professorship Code\u003Cbr>T-76 |\n| Supervisor\u003Cbr>Casper Lassenius |  |  |\n| Instructor\u003Cbr>Casper Lassenius |  |  |\n| Pair programming is an intensive form of programmer collaboration where two programmers design, code and test software collaboratively at one computer. Pair programming has been proposed to provide several benefits for software development. This work studied the effects of pair programming for productivity, defects counts, design quality, knowledge transfer, enjoyment of work, and effort estimation accuracy. The research consisted of an experiment with five four-person teams each doing a 400-hour project based on the same specifications, technologies and process guidelines. The only difference between the teams was that three of the teams used pair programming for all development work and the other teams used solo programming.\u003Cbr>In the experiment pair programming increased the development effort of the first few use cases, but after that there were almost no differences in the use case efforts compared to solo programming. Surprisingly, higher use case complexity did not favor pair programming. Due to the less productive learning time the pair programming teams had worse overall project productivity. However, in an industrial context the causes for the learning time are usually avoided, because developers already know each other and after the first pair programming project are already familiar with the practice. Even if there still were learning time involved, its effects become negligible in a large project.\u003Cbr>The pair programming teams had less pre-delivery but more post-delivery defects. Their attitude towards system testing might have been less careful due to an over-reliance on the peer review taking place during coding. Our efforts at contrasting the resulting design quality were inconclusive.\u003Cbr>Pair programming improved both the breadth and depth of knowledge transfer. In the pair programming teams each code package was understood well by more developers than in the solo programming teams. On the average developers in the pair programming teams also understood well more packages than developers in the solo programming teams.\u003Cbr>About half of the developers in the pair programming teams favored solo programming over pair programming, but still most developers liked working in the pair programming teams. Thus developers’ feelings toward pair programming should not hinder deploying pair programming.\u003Cbr>The pair programming teams were slightly better in estimating efforts required for implementing externally specified use cases early in the project. However, when updating the effort estimate just before the implementation of a use case, solo programmers were accurate more often than pairs.\u003Cbr>These results certainly shed some more light on the topic, even though this experiment, like all the previous ones, contained many deficiencies such as the small sample size. Based on the results, it seems that the use of pair programming leads to fewer defects in code after coding and better knowledge transfer within the development team without requiring additional effort if the learning time can be avoided. These benefits are likely to decrease the further development costs of the system and increase an organizat","cbCaijxxYHJIak2F","https://ap.wps.com/l/cbCaijxxYHJIak2F","pdf",522990,74,"English","[{\"question\":\"How was the experiment set up to compare pair programming and solo programming?\",\"answer\":\"Five four-person teams completed 400-hour projects using the same specifications, technologies, and process guidelines. Three teams used pair programming for all development work, while the other teams used solo programming.\"},{\"question\":\"Did pair programming always improve productivity and effort estimation?\",\"answer\":\"Pair programming increased development effort for the first few use cases, but later use case efforts were almost the same as with solo programming. Effort estimation was slightly better early on for externally specified use cases, but solo programmers were more accurate when updating estimates right before implementation.\"},{\"question\":\"What effects did pair programming have on defects and knowledge transfer?\",\"answer\":\"Pair programming teams had less pre-delivery but more post-delivery defects. Knowledge transfer improved in both breadth and depth, as code packages were understood well by more developers than in the solo programming teams.\"}]","Effects of Pair Programming at the Development Team Level - An Experiment | PDF",1790137740,26]