Extreme Programming Modified Paper

"Extreme Programming Modified: Embrace Requirements Engineering Practices"

a paper by Jerzy Nawrocki, Micha Jasiñski, Bartosz Walter, Adam Wojciechowski of Poznañ University of Technology, Poland

Abstract:

"Extreme Programming (XP) is an agile (lightweight) software development methodology and it becomes more and more popular. XP proposes many interesting practices, but it also has some weaknesses. From the software engineering point of view the most important issues are: maintenance problems resulting from very limited documentation (XP relies on code and test cases only), and lack of wider perspective of a system to be built. Moreover, XP assumes that there is only one customer representative. In many cases there are several representatives (each one with his own view of the system and different priorities) and then some XP practices should be modified. In the paper we assess XP from two points of view: the Capability Maturity Model and the Sommerville-Sawyer Model. We also propose how to introduce documented requirements to XP, how to modify the Planning Game to allow many customer representatives and how to get a wider perspective of a system to be built at the beginning of the project lifecycle."

 Paper:
  http://www.cs.put.poznan.pl/jnawrocki/publica/re02-essen.doc
 related Power Point presentation:
  http://www.cs.put.poznan.pl/jnawrocki/publica/re02-essen.ppt

---

GlenAlleman called this paper to RonJeffries' attention, who posted it in the xpAdoption Yahoo group, to start a discussion:

 http://groups.yahoo.com/group/xpAdoption/message/1

JeffGrigg responded specifically to the suggestion of using the Delphi method for project estimation, explaining how it is overkill if you're estimating user stories and tasks (rather than trying to estimate the whole project at once):

 http://groups.yahoo.com/group/xpAdoption/message/293