I have seen development teams - usually folks who have been working in the industry for many years who have been resistant to pair programming. Often it is due to fear of change and perceived lack of personal space. Are there any ways to ease these concerns and get the development team on board with pair programming?
jonathan cogley
[ Admin ]
There are many positive aspects to Pair Programming for developers:
- Transfer of knowledge to prevent being pigeon-holed into certain tasks
- Learning new technical skills or best practices from others
- More social aspects / better team unity
These aspects should be emphasized and you could do things like keeping a separate desk to preserve personal space for calls, emails, etc.
Note that some personalities are not compatible with Pair Programming (typically those who need quiet to concentrate and prefer to work on their own).