Experimentation in software engineering
IEEE Transactions on Software Engineering
Extreme programming explained: embrace change
Extreme programming explained: embrace change
Case study: extreme programming in a university environment
ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
Empirical Findings in Agile Methods
Proceedings of the Second XP Universe and First Agile Universe Conference on Extreme Programming and Agile Methods - XP/Agile Universe 2002
Contributing to Eclipse: Principles, Patterns, and Plugins
Contributing to Eclipse: Principles, Patterns, and Plugins
Comparing extreme programming to traditional development for student projects
XP'03 Proceedings of the 4th international conference on Extreme programming and agile processes in software engineering
Lessons learned from an XP experiment with students: test-first needs more teachings
PROFES'06 Proceedings of the 7th international conference on Product-Focused Software Process Improvement
Considering rigor and relevance when evaluating test driven development: A systematic review
Information and Software Technology
| Hi-index | 0.00 |
Designing experiments to be carried out with students as subjects in an XP setup is a difficult task: Students lack experiences with XP, there are limited resources, the experiment might not be taken seriously and other effects interfere. This paper presents an experiment using student subjects examining test-first in comparison to classical-testing. We proved several hypotheses about test coverage, number of test-cases, contacts with customer, acceptance for test-first, development speed and not required features. While designing the experiment we noticed that it is useful to include some additional XP techniques on top of test first, because of our special setup and the demands we had. Despite careful planning and conduction of the experiment we still faced a number of problems. In this paper we also discuss the problems with our experimental setup.