Advances in software inspections
IEEE Transactions on Software Engineering
An analysis of defect densities found during software inspections
Journal of Systems and Software
Evaluating the cost of software quality
Communications of the ACM
The costs and benefits of pair programming
Extreme programming examined
Peer reviews in software: a practical guide
Peer reviews in software: a practical guide
Software Inspection: An Industry Best Practice for Defect Detection and Removal
Software Inspection: An Industry Best Practice for Defect Detection and Removal
Pair Programming Illuminated
Software Inspection
Software Inspections: An Effective Verification Process
IEEE Software
Process Improvement and the Corporate Balance Sheet
IEEE Software
Lessons from Three Years of Inspection Data
IEEE Software
What We Have Learned About Fighting Defects
METRICS '02 Proceedings of the 8th International Symposium on Software Metrics
Balancing Agility and Discipline: A Guide for the Perplexed
Balancing Agility and Discipline: A Guide for the Perplexed
The collaborative software process(sm)
The collaborative software process(sm)
The Impact of Using Pair Programming on System Evolution: A Simulation-Based Study
ICSM '04 Proceedings of the 20th IEEE International Conference on Software Maintenance
Improving quality through software process improvement in Thailand: initial analysis
3-WoSQ Proceedings of the third workshop on Software quality
The economic impact of software process variations
ICSP'07 Proceedings of the 2007 international conference on Software process
Proceedings of the 34th International Conference on Software Engineering
Hi-index | 0.00 |
Although pair programming and software inspection have the common aim of minimizing the defects of the software product, each practice has its strengths and weaknesses. We need to understand their costs and benefits under given conditions to be able to select a practice to execute in a development project. The objective of this study is to compare the commonalities and differences between pair development and software inspection as verification techniques in Thailand. One classroom experiment and one industry experiment were conducted. The development effort and effect of quality were investigated with some additional calendar time comparisons. The classroom results showed that average development effort of the pair development group was 24% less than inspection group with the improved product quality. The industry experiment showed pair development to have about 4% more effort but about 40% fewer major defects. In addition, the impacts of cultural differences to the adoption of pair programming or software inspection in Thailand are discussed.