San Francisco, California
London, United Kingdom
Abstract: Even after all these years (the first documented experiment took place in 1975), pair programming continues to be one of the most controversial software development practices.
Despite all the discussion, research, and practical application of the technique, people usually debate pair programming from a purely emotional standpoint, often based on speculation and not direct experience. The stridency and circularity of discussions about pairing led the presenters to wonder exactly what factors contribute to good outcomes from pair programming, what factors might cause poor outcomes, what decisions factors we ought to use to choose when to pair, and what new skills we can develop to enable us to overcome the initial barriers and take full advantage of the practice.
In this session we want to explore the kinds of issues coaches and change agents encounter when introducing teams to pairing, and ways they can help people understand how pairing affects the work, when to use it and when not to use it.
Speaker Bio: Mike Bowler, Agile & Technical Coach
One of the very early agile practitioners, Mike has been helping his clients with agile practices and implementations since 2000. He blends his strong technical background with a deep understanding of Agile methods to help teams consistently deliver higher quality products. http://www.gargoylesoftware.com/mike_bowler
Spealer Bio: Dave Nicolette, Agile & Technical Coach
Dave is a consultant specializing in improving software development and delivery methods and practices, with particular interest in coaching and mentoring individuals and teams. He can provide process assessment, training classes, workshops, and coaching and mentoring services in the management, technical, and human factors aspects of contemporary software delivery practice, combining agile and lean values and principles with proven traditional methods.