Essays collection 2012
Home Home SK
"pair programming"
Fornádeľ Michal

Abstract. Pair programming as a part of extreme programming is based on active cooperation of two programmers working on the same task side by side. Regarding the increase of efficiency and the quality, it is absolutely significant to identify mutual activities and refuse to program in pair all the time. Different character qualities, abilities of programmers and the type of project are relevant for considering the fact if pair programming is suitable technique for usage. From the theoretical point of view, advantages of pair programming are very beneficial for both members of development team and managers who reduce financial resources and qualitatively increase the level of project. Unfortunately, the practical experiences have shown that many programmers are a bit skeptical because of difficulty according to the time synchronization of pair, mutual misunderstanding, personal discomfort, feeling of endless control and loss of concentration. Pair programming is suitable for activities demanding further investigation and different conceptual views. Other activities from the programmer’s point of view could bring some disadvantages.


Kocian Róbert

Abstract. Requirements for faster software development and quality are getting higher and higher, so for programmers it is more and more challenging. Development of a high-quality and comprehensive application with continuously increasing requirements is extremely difficult task in this accelerating time so this situation requires the use of extreme development methods making this problem largely eliminated so it is possible to develop high-quality software in the shortest time. Appropriate use of pair programming depends on the size of the project as well as the size of the team. This leads to question. Is Pair programming a suitable method for small teams working on smaller projects? If so, is it possible to do pair programming in smaller teams in order to achieve the required criteria imposed on the project?


Left Separator
monitoring software project metrics function points plan planning software product risk management test driven development error effective communication sofware metrics software development team problems development software quality development support management extreme programming pair programming Scrum communication relations control progress subversion git critical path method project planning estimation agile development risks motivation requirement collection testing use case points support tools support tools outsourcing team size estimation version management quality cooperation risk documentation project software versioning conflict