Field Experiences with eXtreme Programming: Developing an Emergency Response System

References

• Abrahamsson, P., and Koskel, J. eXtreme programming: A survey of empirical data from a controlled case study. In N. Juristo and F. Shull (eds.), Proceedings of the ACM-IEEE International Symposium on Empirical Software Engineering. Los Alamitos, CA: IEEE Computer Society Press, 2004, pp. 73-82.
   Google Scholar
• Anderson, A.; Beattie, R.; and Beck, K.; Bryant, D.; DeArment, M.; Fowler, M.; Fronczak, M.; Garzaniti, R.; Gore, D.; Hacker, B.; Hendrickson, C.; Jeffries, R.; Joppie, D.; Kim, D.; Kowalsky, P.; Mueller, D.; Murasky, T.; Nutter, R.; Pantea, A.; and Thomas, D. Chrysler goes to "extremes." Distributed Computing, 11 (October 1998), 24-28.
   Google Scholar
• Argyris, C.; Putnam, R.; and MacLain Smith, D. Action Science--Concepts, Methods and Skills for Research and Intervention. San Francisco: Jossey-Bass, 1982.
   Google Scholar
• Armitage, J. Are agile methods good for design? Interaction, 11, 1 (January-February 2004), 14-23.
   Google Scholar
• Astels, D.; Miller, G.; and Novak, M. A Practical Guide to eXtreme Programming. Upper Saddle River, NJ: Prentice Hall, 2002.
   Google Scholar
• Auer, K., and Miller, R. eXtreme Programming Applied. Boston: Addison-Wesley, 2002.
   Google Scholar
• Baskerville, R.L. Investigating information systems with action research. Communications of the AIS, 2, 19 (1999), 1-32.
   Google Scholar
• Beck, K. Embracing change with eXtreme programming. IEEE Computer, 32, 10 (1999), 70-77.
   Google Scholar
• Beck, K. eXtreme Programming Explained. Boston: Addison-Wesley, 2000.
   Google Scholar
• Beck, K.; Beedle, M.; van Bennekum, A.; Cockburn, A.; Cunningham, W.; Fowler, M.; Grenning, J.; Highsmith, J.; Hunt, A.; Jeffries, R.; Kern, J.; Marick, B.; Martin, R.C.; Mellor, S.; Schwaber, K.; Sutherland, J.; and Thomas, D. Manifesto for agile software development. Agile Aliance, Snowbird, UT, 2001 (available at www.agilemanifesto.org).
   Google Scholar
• Biffl, S.; Aurum, A.; Boehm, B.; Erdogmus, H.; and Grünbacher P. (eds). Value-Based Software Engineering. Berlin: Springer-Verlag, 2005.
   Google Scholar
• Boehm, B.W. A spiral model of software development and enhancement. IEEE Computer, 21, 5 (May 1988), 61-72.
   Google Scholar
• Boehm, B.W. Get ready for agile methods with care. IEEE Computer, 35, 1 (2002), 64-69.
   Google Scholar
• Boehm, B.W. Value-based software engineering. Software Engineering Notes, 28, 2 (2003), 1-12.
   Google Scholar
• Cao, L.; Mohan, K.; Xu, P.; and Ramesh, B. How extreme does programming have to be? Adapting XP practices to large-scale projects. In R.H. Sprague (ed.), Proceedings of the Thirty-Seventh Hawaii International Conference on System Sciences. Los Alamitos: IEEE Computer Society Press, 2004 (available at csdl2.computer.org/comp/proceedings/hicss/2004/2056/03/ 205630083c.pdf).
   Google Scholar
• Checkland, P.B. Systems Thinking, Systems Practice. Chichester, UK: John Wiley & Sons, 1981.
   Google Scholar
• Cockburn, A. Agile Software Development. Reading, MA: Addison-Wesley, 2001.
   Google Scholar
• Cockburn, A., and Highsmith, J. Agile software development: The people factor. IEEE Computer, 34, 11 (2001), 131-133.
   Google Scholar
• Cockburn, A., and Williams, L. The costs and benefits of pair programming. In Proceedings of eXtreme Programming and Flexible Processes in Software Engineering. Cagliari, Italy, 2000, pp. 223-243.
   Google Scholar
• Elssamadisy, A., and Schalliol, G. Recognizing and responding to bad smells in eXtreme programming. In J. Magee and M. Young (eds.), Proceedings of the Twenty-Fourth International Conference on Software Engineering. New York: ACM Press, 2002, pp. 617-622.
   Google Scholar
• Glass, R. Matching methodology to problem domain. Communications of the ACM, 47, 5 (May 2004), 19-21.
   Google Scholar
• Grünbacher, P.; Halling, M.; Biffl, S.; Kitapci, H.; and Boehm, B.W. Integrating collaborative processes and quality assurance techniques: Experiences from requirements negotiation. Journal of Management Information Systems, 20, 4 (Spring 2004), 9-29.
   Google Scholar
• Hansson, C., and Winter, J. Agile processes for small public projects and PD outside of office hours. In P. Flensburg (ed.), Proceedings of the Twenty-Seventh Information Systems Research Seminar in Scandinavia. Göteborg: IRIS Association, 2004, pp. 1-17.
   Google Scholar
• Hickey, A.M., and Davis, A.M. A unified model of requirements elicitation. Journal of Management Information Systems, 20, 4 (Spring 2004), 65-84.
   Google Scholar
• Highsmith, J., and Cockburn, A. Agile software development: The business innovation. Computer, 34, 9 (September 2001), 120-122.
   Google Scholar
• Iivari, J.; Hirschheim, R.; and Klein, H.K. A dynamic framework for classifying information systems development methodologies and approaches. Journal of Management Information Systems, 17, 3 (Winter 2000-2001), 179-218.
   Google Scholar
• Jeffries, R. eXtreme testing. Software Testing & Quality Engineering, 1, 2 (March-April 1999), 23-26.
   Google Scholar
• Karlstrom, D. Introducing eXtreme programming--An experience report. In Proceedings of the Third International Conference on eXtreme Programming and Agile Processes in Software Engineering. Sardinia, Italy, 2002, pp. 24-29.
   Google Scholar
• Keefe, K., and Dick, M. Using eXtreme programming in a capstone project. In R. Lister and A. Young (eds.), Proceedings of the Sixth Australian Computing Education Conference. Darlinghurst, Australia: Australian Computer Society, 2004, pp. 151-161.
   Google Scholar
• Keefer, G. Pair programming: An alternative to reviews and inspections? Cutter IT Journal, 18, 1 (2005), 14-19.
   Google Scholar
• Lethbridge, T.C.; Singer, J; and Forward, A. How software engineers use documentation: The state of the practice. IEEE Software, 20, 6 (2003), 35-39.
   Google Scholar
• Lippert, M.; Beck-Pechau, P.; Breitling, H.; Koch, J.; Kornstadt, A.; Roock, S.; Schmolitsky, A.; Wolf, H.; and Zullighoven, H. Developing complex projects using XP with extensions. IEEE Computer, 36, 6 (2003), 67-71.
   Google Scholar
• Martin, R. eXtreme programming development through dialog. IEEE Software, 17, 4 (2000), 12-13.
   Google Scholar
• Martin, R. Agile Software Development: Principles, Patterns, Practice. Upper Saddle River, NJ: Pearson Education, 2003.
   Google Scholar
• McMahon, J. Five lessons from transitioning to eXtreme programming. Control Engineering, 50, 3 (March 2003), 59-65.
   Google Scholar
• Muller, M.M., and Padberg, F. On the economic evaluation of XP projects. In P. Inverardi (ed.), Proceedings of the Ninth European Software Engineering Conference Held Jointly with the Tenth ACM SIGSOFT International Symposium on Foundations of Software Engineering. New York: ACM Press, 2003, pp. 168-177.
   Google Scholar
• Myers, M.D. Qualitative research in information systems. ISWorld Net, June 1997 (available at www.qual.auckland.ac.nz).
   Google Scholar
• Padberg, F., and Muller, M.M. Analyzing the cost and benefit of pair programming. In B. Werner (ed.), Proceedings of the Ninth International Software Metrics Symposium. Los Alamitos, CA: IEEE Computer Society Press, 2003, pp. 166-179.
   Google Scholar
• Poole, C.; Murphy, T.; Huisman, J.; and Higgins, A. Extreme maintenance. In G. Canfora and A. Amschler Andrews (eds.), Proceedings of the Seventeenth IEEE International Conference on Software Maintenance. Los Alamitos, CA: IEEE Computer Society Press, 2001, pp. 301-312.
   Google Scholar
• Saleem, N. An empirical test of the contingency approach to user participation in information systems development. Journal of Management Information Systems, 13, 1 (Summer 1996), 145-166.
   Google Scholar
• Schach, S.R. An Introduction to Object-Oriented Systems Analysis and Design with UML and the Unified Process. Boston: McGraw-Hill, 2004.
   Google Scholar
• Schwaber, K., and Beedle, M. Agile Software Development with Scrum. Englewood Cliffs, NJ: Prentice Hall, 2001.
   Google Scholar
• Shore, J. Continuous design. IEEE Software, 21, 1 (2004), 20-22.
   Google Scholar
• Smith, S., and Stoecklin, S. What we can learn from eXtreme programming. Journal of Computing in Small Colleges, 17, 2 (2001), 144-151.
   Google Scholar
• Sommerville, I. Software Engineering. Boston: Addison-Wesley, 2004.
   Google Scholar
• Standish Group. The CHAOS report into project failure. West Yarmouth, MA, 1994 (available at standishgroup.com/visitor/PDFpages/chaos1994.pdf).
   Google Scholar
• Stephens, M., and Rosenberg, D. The irony of eXtreme programming. Dr. Dobbs Journal, 29, 5 (2004), 44-47.
   Google Scholar
• Turner, R., and Boehm, B.W. People factors in software management: Lessons from comparing agile and plan-driven methods. CrossTalk, The Journal of Defense Software Engineering, 10, 12 (2003), 4-8.
   Google Scholar
• Turoff, M.; Chumer, M.; Hiltz, R.S.; Klashner, R.; Alles, M.; Vasarhelyi, M.; and Kogan, A. Assuring homeland security: Continuous monitoring, control and assurance of emergency preparedness. Journal of Information Technology Theory and Application, 6, 3 (2004), 1-24.
   Google Scholar
• Watson, R.T.; Kelly, G.G.; Galliers, R.D.; and Brancheau, J.C. Key issues in information systems management: An international perspective. Journal of Management Information Systems, 13, 4 (Spring 1997), 91-115.
   Google Scholar
• Zuber-Skerritt, O. Action Research for Change and Development. Aldershot, UK: Gower, 1991.
   Google Scholar