Are Two Heads Better than One for Software Development? The Productivity Paradox of Pair Programming

Balijepally,; Mahapatra,; Nerur,; Price, '

doi:10.2307/20650280

Cited by 107 publications

(75 citation statements)

References 0 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Refactoring is used to evolve the underlying architecture and design in order to accommodate new functionality (Mens and Tourwe, 2004). Pair programming, where developers work together in a manner analogous to a pilot/co-pilot configuration, has been studied extensively (Balijepally et al, 2009;Lui et al, 2008). Effective XP teams have a shared sense of responsibility, and a relaxed yet rhythmic approach to working; and good quality code is a jointly-owned and valued asset (Sharp and Robinson, 2004).…”

Section: Agile Methodsmentioning

confidence: 99%

How product owner teams scale agile methods to large distributed enterprises

Bass

2014

Empir Software Eng

113

View full text Add to dashboard Cite

Software development teams in large scale offshore enterprise development programmes are often under intense pressure to deliver high quality software within challenging time contraints. Project failures can attract adverse publicity and damage corporate reputations. Agile methods have been advocated to reduce project risks, improving both productivity and product quality. This article uses practitioner descriptions of agile method tailoring to explore large scale offshore enterprise development programmes with a focus on product owner role tailoring, where the product owner identifies and prioritises customer requirements. In globalised projects, the product owner must reconcile competing business interests, whilst generating and then prioritising large numbers of requirements for numerous development teams. The study comprises eight international companies, based in London, Bangalore and Delhi. Interviews with 46 practitioners were conducted between February 2010 and May 2012. Grounded theory was used to identify that product owners form into teams. The main contribution of this research is to describe the nine product owner team functions identified: groom, prioritiser, release master, technical architect, governor, communicator, traveller, intermediary and risk assessor. These product owner functions arbitrate between conflicting customer requirements, approve release schedules, disseminate architectural design decisions, provide technical governance and propogate information across teams. The functions identified in this research are mapped to a scrum of scrums process, and a taxonomy of the functions shows how focusing on either decision-making or information dissemination in each helps to tailor agile methods to large scale offshore enterprise development programmes.Keywords agile software development · scrum · large scale offshore enterprise development programmes · product owner · product owner teams · grounded theory.

show abstract

Section: Agile Methodsmentioning

confidence: 99%

How product owner teams scale agile methods to large distributed enterprises

Bass

2014

Empir Software Eng

113

View full text Add to dashboard Cite

show abstract

“…The meaning of "success" to Free Software projects was discussed from different perspectives in previous research: (i) source code modularity [22]; (ii) number of lines of code generated [23]; (iii) velocity of closing bugs [6]; (iv) ability of a project to advance through development phases (e.g., from alpha to beta to stable) [21], [20]; (v) number of downloads [24]; (vi) number of members [25].…”

Section: B Attractivenessmentioning

confidence: 99%

A Study of the Relationships between Source Code Metrics and Attractiveness in Free Software Projects

Meirelles

Santos

Miranda

et al. 2010

2010 Brazilian Symposium on Software Engineering

View full text Add to dashboard Cite

Abstract-A significant number of Free Software projects has been widely used and considered successful. However, there is an even larger number of them that cannot overcome the initial steps towards building an active community of users and developers. In this study, we investigated whether there are relationships between source code metrics and attractiveness, i.e., the ability of a project to attract users and developers. To verify these relationships, we analyzed 6,773 Free Software projects from the SourceForge.net repository. The results indicated that attractiveness is indeed correlated to some source code metrics. This suggests that measurable attributes of the project source code somehow affect the decision to contribute to and adopt a Free Software. The findings described in this paper show that it is relevant for project leaders to monitor source code quality, particularly a few objective metrics, since these can have a positive influence in projects chances of forming a community of contributors and users around their software, enabling further enhancement in quality.

show abstract

“…Pair programming, where developers work together in a manner analogous to a pilot/co-pilot configuration, has been studied extensively [17] [18] [19].…”

Section: Agile Methodsmentioning

confidence: 99%