Software Process Improvement

Extreme programming (XP), similarly to other agile software development methods, values close collaboration with customers. One of the XP practices suggests that the customer should be 100% available for the development team. Anecdotal evidence suggests that the XP customer role is costly, difficult and demanding. However, very few empirical studies have been published on the role of customer in an XP project. The results of this controlled case study are in line with the common belief that the on-site customer’s role is indeed demanding, requiring a strong ability to resolve issues rapidly. Yet, the study also offers contrasting findings in terms of required actual customer involvement in the development project. This empirical case demonstrates that while the customer was present close to 100% with the development team, only 21% of his work effort was required to assist the team in the development. However, it is also shown that an on-site customer may create a false sense of confidence in the system under development. The implications of these and other findings are discussed.

[1]  James C. McKim,et al.  Using a multiple term project to teach object oriented programming and design , 2004, 17th Conference on Software Engineering Education and Training, 2004. Proceedings..

[2]  Kurt Schneider Active Probes Synergy in Experience-Based Process Improvement , 2000, PROFES.

[3]  Donald A. Sch The reflective practitioner: how professionals think in action , 1983 .

[4]  Bill Culleton,et al.  Process Improvement for Small Organizations , 1999, Computer.

[5]  Herb Krasner,et al.  Accumulating the Body of Evidence for The Payoff of Software Process Improvement , 1997 .

[6]  Victor R. Basili,et al.  Experience in Implementing a Learning Software Organization , 2002, IEEE Softw..

[7]  Terttu Orci,et al.  Dynamic CMM for Small Organisations - Implementation Aspects , 2000 .

[8]  Deependra Moitra,et al.  Managing change for software process improvement initiatives: a practical experience-based approach , 1998, Softw. Process. Improv. Pract..

[9]  Doris Schmedding,et al.  Ein Prozessmodell für das Software-Praktikum , 2001, SEUH.

[10]  Claus Lewerentz,et al.  Die Rolle der Reflexion in Softwarepraktika , 2001, SEUH.

[11]  Pasi Kuvaja Software Process Assessment and Improvement: The BOOTSTRAP Approach , 1994 .

[12]  Austen Rainer,et al.  Key success factors for implementing software process improvement: a maturity-based analysis , 2002, J. Syst. Softw..

[13]  Kurt Schneider What to Expect from Software Experience Exploitation , 2002, J. Univers. Comput. Sci..

[14]  M. Brian Blake,et al.  Teaching an object-oriented software development lifecycle in undergraduate software engineering education , 2002, Proceedings 15th Conference on Software Engineering Education and Training (CSEE&T 2002).

[15]  Karlheinz Kautz,et al.  Software process improvement in very small enterprises: does it pay off? , 1998, Softw. Process. Improv. Pract..