author = {Kai Stapel and Daniel Lübke and Eric Knauss},
  title = {{B}est {P}ractices in e{X}treme {P}rogramming {C}ourse {D}esign},
  booktitle = {Proceedings of the 30th International Conference on Software Engineering
	(ICSE '08)},
  year = {2008},
  pages = {769-776},
  address = {Leipzig, Germany},
  month = {May},
  organization = {Association for Computer Machinery},
  publisher = {ACM Press},
  abstract = {Teaching (and therefore learning) eXtreme Programming (XP) in a university
	setting is difficult because of course time limitations and the soft
	nature of XP that requires first-hand experience in order to see
	and really learn the methods. For example, iterations are either
	shorter or fewer than appropriate. In this paper we present the properties
	to tune when designing an eXtreme Programming course. These are the
	properties we gathered by conducting three XP labs as part of our
	software engineering teaching. Within this paper we describe our
	set-up as well as the important properties. Lecturers and teachers
	can use this property system and combine it with their own constraints
	in order to derive a better XP lab for their curriculum.},
  doi = {10.1145/1368088.1368197},
  url = {}