Browse Prior Art Database

System for associating collaboration data generated during Pair Programming with an active task or change set

IP.com Disclosure Number: IPCOM000198204D
Publication Date: 2010-Jul-29
Document File: 2 page(s) / 21K

Publishing Venue

The IP.com Prior Art Database

Abstract

Disclosed is a system for associating collaboration data generated during pair programming with an active task or change set

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 52% of the total text.

Page 1 of 2

System for associating collaboration data generated during Pair Programming with an active task or change set

Pair Programming is a common Agile software practice that involves 2

programmers working

together and collaborating synchronously on the same software artifact. Many tools exist today that are designed to enable programmers who are not in the same location to pair program, and often audio and video links are established to help remote pair programmers to collaborate with each other more effectively.

An opportunity that arises when doing remote pair programming is the ability to easily log this collaboration. Often, when two programmers are standing in the same cube or writing on a white board, none of the discussion is captured, only the outcome. And white boards often get erased without capturing the information in a more permanent format. This is a problem when a

programmer needs to recall why a design decision was made or a previous discussion about how

to fix a bug.

With remote pair programming, audio, video, or other collaboration information can sometimes be captured, but then the programmers must manually mange that data in such a way that it can be referenced again later.

Our method involves a system where collaboration information is automatically recorded, stored, associated with the change set in a source control system or active task in a change management system. As a pair of developers work on different tasks, the collaboration information (for example, video, audio or audio transcript, file changes and who made them, etc) gets logged and stored in the change management/source control system. This could happen unobtrusively and would not interrupt the pair programmers, or the programmers could be prompted if the

programmers consent to logging the collaboration.

The advantage of this concept is that it captures this collaboration information automatically and becomes an integral part of the softwa...