Article List

I have failed a sprint

by Mohamed El-Deeb (2008-11-09)
Rating (0 ratings) read comments

Some lessons learned from one of the tough sprints I managed

Are Two Heads Better than One? On the Effectiveness of Pair Programming

by Tore Dybå, Erik Arisholm, Dag Sjøberg, Jo Hannay, Forrest Shull (2007-11-15)
Rating (0 ratings) read comments

Many developers, and not just those who have ended up programming alone in windowless offices, have been excited by pair programming (PP), while others seem extremely annoyed by it. In both cases, perhaps the most important result is that PP leads to rethinking about the concept of development teams and about how individual programmers can best contribute to the project. Now that PP is several years old and has seen increasing interest and adoption, it’s useful to consider what has been learned about its more specific effects. In this article, we systematically reviewed all articles to date that compared the effects of PP and of individual programming. The evidence certainly provides proof of its benefit, although not in all cases and perhaps not in the contexts that many developers would have thought.

Paired Programming - benefits for team and individual development

by Siobhan Walsh (2007-04-25)
Rating (0 ratings) read comments

Article examining benefits of paired programming in relation to of shared knowledge and whole team development.

10 Key Principles of Agile Development

by kelly.waters (2007-02-10)
Rating 5.0 out of 5 (1 rating) read comments

10 Key Principles of Agile Development

Two Heads, One Focus

by Nedland, Magnar (2005-04-01)
Rating 4.0 out of 5 (1 rating) read comments

Magnar discusses his experience with pair programming – the good and the bad. He raises the interesting subject of the impact of personal interactions and their impact on productivity. Maybe pair programming isn’t for everyone or every group, but when it is in place with the right personalities it does seem to have many benefits.

Pair Programming Observations

by Langr, Jeff (2005-01-09)
Rating 5.0 out of 5 (1 rating) read comments

Observations and thoughts on pair programming.

Knowledge Transfer through Asymmetric Pair Programming

by Ye, Young; Fay, Royce (2004-12-02)
Rating 4.0 out of 5 (3 ratings) read comments

This paper uses a case study to demonstrate how the eXtreme Programming methodology can be adapted into a knowledge transfer process between an IT consultant and a domain user. It also includes refactoring software, and documenting the process so that all other domain users can work on the repeatable process.

Hearts as Weapons

by Jeffries, Ron (2004-09-21)
Rating 3.0 out of 5 (1 rating) read comments

Ron utilizes cards to describe the intricate communications that occur, the relationship between work and home life, etc. Intrapersonal relationships are a major driving factor in all projects – either in a positive or negative direction; they can determine productivity, quality of product, quality of life and is one area often ignored in most project management discussions.

A Field Study of Developer Pairs: Productivity Impacts and Implications

by Allen Parrish, Randy Smith, David Hale, and Joanne Hale (2004-09-01)
Rating 4.0 out of 5 (1 rating) read comments

The authors build from a previous study of programmer productivity as team size increases, where they had concluded that increased concurrent work on core modules leads to decreased productivity. They reconsider their data for concurrent working pairs in response to positive findings from pair programming. The authors conclude that the role-based coordination protocol associated with agile software methodologies overcomes a significant productivity loss otherwise associated with concurrent software development pairs.