Nov 12, 2013 · 7:00 PM
Laurie Williams, North Carolina State University
Two people working at one computer collaborating on the same deliverable – sounds like a route to double expenses. Not so. Pair programming leads to higher quality code, better solutions, knowledge management, and risk reduction without any significant productivity hit. And, pairing can be used throughout the software development lifecycle not just during programming as the popular term pair programming can imply. Some software development teams pair all day, every work day, on all tasks. More commonly, teams practice “on demand” pairing to solve problems or to train new team members. Laurie will describe the benefits and the resistances she’s seen with teams that utilize pairing. She will also discuss “partner picking principles” in which the right engineers collaborate based upon the task at hand.
For more than thirteen years, Laurie Williams has been working with development teams to both train and coach them to transition to the use of agile software development practices as well as to evaluate whether the transition was beneficial for the team in terms of quality and productivity improvements. Co-author of Pair Programming Illuminated, Laurie’s inaugural agile study published in 2000 demonstrated that pair programmers produced higher quality code in essentially the same amount of total time as solo programmers. Laurie, a professor of computer science at North Carolina State University, can be reached at [masked].