Managing technical people: innovation, teamwork, and the software process
Managing technical people: innovation, teamwork, and the software process
The case for collaborative programming
Communications of the ACM
Pair Programming Illuminated
Strengthening the Case for Pair Programming
IEEE Software
Extreme Programming from a CMM Perspective
IEEE Software
The Effects of "Pair-Pressure" and "Pair-Learning" on Software Engineering Education
CSEET '00 Proceedings of the 13th Conference on Software Engineering Education & Training
The collaborative software process(sm)
The collaborative software process(sm)
Knowledge Sharing: Agile Methods vs. Tayloristic Methods
WETICE '03 Proceedings of the Twelfth International Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises
| Hi-index | 0.00 |
It has been long recognized that the quality of the people employed by a software organization is a major determinant of the quality of its products. Acknowledging the pivotal role played by people in software development, the Software Engineering Institute (SEI) devised the People - Capability Maturity Model. Like its software counterpart, the People CMM (P-CMM) defines five levels of maturity. An organization can achieve a level by institutionalizing the "best practices" for that level. The best practices are grouped together as Key Process Areas (KPAs). Pair programming is a practice in which two programmers work together at one computer on a single module of code - designing, coding and testing it together. Evidence indicates that pair programming improves teamwork, communication and knowledge levels - all KPAs of the P-CMM. This paper establishes a link between pair programming and the KPAs defined in the P-CMM. Specifically, the paper provides an outline on the advantages and effects of adopting pair programming if an organization wants to achieve a higher P-CMM level.