@inproceedings {SE.5.Gallis.2002,
	title = {A Transition From Partner Programming to Pair Programming - an Industrial Case Study},
	journal = {Workshop "Pair Programming Installed" in 17th Annual ACM Conference on Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA), Position paper},
	year = {2002},
	month = {November 4-8},
	publisher = {-},
	type = {1},
	address = {Seattle USA},
	abstract = {Pair programming is believed to provide many benefits compared with individual programming. However, implementing pair programming in a development project may not be trivial. At present, we are studying a small, industrial development project with two distributed pairs. Data has been collected through daily diaries, task questionnaires, feedback meetings and observation of the pairs. The preliminary results show that the two pairs are struggling to convert from their usual {\textquotedblleft}partner programming{\textquotedblright} habits to pair programming. We believe the main reason is that they mostly are used to working on their own individual tasks, but in close cooperation with another programmer in the same physical room (i.e., {\textquotedblleft}partner programming{\textquotedblright}). They are not convinced that a more structured collaboration (i.e., pair programming) will provide additional benefits. There is also a great difference between the pairs in the degree of resistance to pair programming. It seems that the pair with more experience and more knowledge about the system as a whole is more resistant to pair programming than the inexperienced pair. We believe that future empirical studies need to compare pair programming with other kinds of programmer collaboration, such as partner programming and team collocation. Research on pair programming should address when and how the various types of programmer collaboration are beneficial.},
	author = {Gallis, H. and Arisholm, Erik and Dyb{\r a}, Tore}
}
