Method and developer characteristics for effective agile method tailoring: A study of xp expert opinion

ACM Transactions on Software Engineering and Methodology

Volumn 20, Issue 1, 2010, Pages

  Conboy, Kieran ^a   Fitzgerald, Brian ^b  

^a NATIONAL UNIVERSITY OF IRELAND   (Ireland)

^b UNIVERSITY OF LIMERICK   (Ireland)

Author keywords

Agile method; Contingency; Engineering; Expert opinion; Extreme programming; Software development; Tailoring; Xp

Indexed keywords

AGILE METHOD; AGILE METHODS; EXPERT OPINION; EXTREME PROGRAMMING; LITTLE RESEARCH; SOFTWARE DEVELOPMENT; SOFTWARE METHODS;

COMPUTER SOFTWARE; RESEARCH;

SOFTWARE DESIGN;

EID: 77954368560     PISSN: 1049331X     EISSN: 15577392     Source Type: Journal    
DOI: 10.1145/1767751.1767753     Document Type: Article

References (101)

1. ABRAHAMSSON, P., SALO, O., RONKAINEN, J., AND WARSTA, J. 2002. Agile Software Development Methods: Review and Analysis. VTT Publications, Technical Research Centre of Finland, Espoo, Finland, 478.
2. ÅGERFALK, P. AND FITZGERALD, B. 2005. Methods as action knowledge: Exploring the concept of method rationale in method construction, tailoring and use. In Proceedings of the 10th IFIP WG8.1 International Workshop on Exploring Modeling Methods in Systems Analysis and Design (EMMSAD).
3. ÅGERFALK, P. AND WISTRAND, K. 2003. Systems development method rationale: A conceptual framework for analysis. In Proceedings of the 5th International Conference on Enterprise Information Systems (ICEIS).
4. AMBLER, S. 2007. Survey says...agile has crossed the chasm. Dr. Dobb's J. World of Softw. Develop. 32, 8, 59-61.
5. AMBLER, S. W. 2002. Agile Modeling: Best Practices for the Unified Process and Extreme Programming. John Wiley & Sons, New York, NY.
6. AUER, K. AND MILLER, R. 2002. Extreme Programming Applied-Playing to Win. Addison-Wesley, Reading, MA.
7. AVISON, D. AND FITZGERALD, G. 2003. Information Systems Development: Methodologies, Techniques and Tools. McGraw-Hill, London, U. K.
8. AVISON, D. AND WOOD-HARPER, A. 1991. Multiview: An Exploration in Information Systems Development. Blackwell Scientific Publications, Oxford, U. K.
9. AYDIN, M. AND HARMSEN, F., ET AL. 2004. An agile informations systems development method in use. Turk. J. Electron. Eng. 12, 2, 127-138.
10. BASKERVILLE, R. AND STAGE, J. 2001. Accommodating emergent work practices: Ethnographic choice of method fragments. In Realigning Research and Practice in Is Development: The Social and Organizational Perspective, B. FitzGerald, N. Russo, and J. DeGross, Eds. Kluwer, New York, NY, 12-28.
11. BASKERVILLE, R., AND TRAVIS, J., ET AL. 1992. Systems without method: The impact of new technologies on information systems development projects. In The Impact of Computer Supported Technologies on Information Systems Development, K. Kendall, J. DeGross, and K. Lyytinen, Eds. North Holland, Elsevier Science Publishers, Amsterdam, The Netherlands, 241-269.
12. BECK, K. 2000. Extreme Programming Explained: Embrace Change. Addison-Wesley, Reading, MA.
13. BECK, K. AND ANDRES, C. 2004. Extreme Programming Explained, 2nd ed. Addison Wesley, Reading, MA.
14. BECK, K. AND BOEHM, B. 2003. Agility through discipline: A debate. IEEE Comput. 36, 6, 44-46.
15. BECK, K. AND FOWLER, M. 2001. Planning eXtreme Programming. Addison-Wesley, Boston, MA.
16. BENYON, D. AND SKIDMORE, S. 1987. Towards a toolkit for the systems analyst. Comput. J. 30, 1, 2-7.
17. BOEHM, B. AND TURNER, R. 2003. Using risk to balance agile and plan-driven methods. IEEE Softw. 36, 6, 57-66.
18. BOEHM, B. AND TURNER, R. 2004. Balancing Agility and Discipline: A Guide For the Perplexed. Addison-Wesley, Boston, MA.
19. BOOCH, G. 1994. Object-Oriented Analysis and Design with Applications. Benjamin Gummings Publishers, Redwood City, CA.
20. BOWERS, J., MAY, J., ET AL. 2002. Tailoring XP for Large Mission Critical Software Development. XP/Agile Universe, Chicago, IL.
21. BRINKKEMPER, S. 1996. Method engineering: Engineering of information systems development methods and tools. Inform. Softw. Tech. 38, 4, 275-280.
22. BRINKKEMPER, S., SAEKI, M. ET AL. 1998. Assembly techniques for method engineering. In Advanced Information Systems Engineering, G. Goos, J. Hartmanis, and J. van Leeuwen, Eds. Springer, Berlin, Germany, 381-390.
23. BRINKKEMPER, S., SAEKI, M., ET AL. 1999. Meta-modelling based assembly techniques for situational method engineering. Inform. Syst. 24, 3, 209-228.
24. BROOKS, F. 1975. The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley, Reading, MA.
25. BROOKS, F. 1987. No silver bullet: Essence and accidents of software engineering. IEEE Comput. 20, 4, 10-19.
26. BROWN, B. 1968. Delphi Process: A Methodology Used for the Elicitation of Opinions of Experts. RAND Corporation, Santa Monica, CA.
27. CAO, L., MOHAN, K., ET AL. 2004. How extreme does extreme programming have to be? Adapting XP practices to large-scale projects. In Proceedings of the 37th Hawaii International Conference on System Sciences. IEEE Computer Society Press, Los Alamitos, CA.
28. CLAYTON, M. 1997. Delphi: A technique to harness expert opinion for critical decision-making tasks in education. Edu. Psychol. 17, 4, 373-387.
29. COAD, P. AND PALMER, S. 2002. Feature-Driven Development. Prentice Hall, Englewood Cliffs, NJ.
30. COCKBURN, A. 2001. Crystal Clear: A Human-Powered Software Development Methodology for Small Teams. Addison-Wesley, Reading, MA.
31. COCKBURN, A. 2002. Agile Software Development. Addison-Wesley, Reading, MA.
32. COLEMAN, D., ARNOLD, P., ET AL. 1994. Object Oriented Development: The Fusion Method. Prentice-Hall, Englewood Cliffs.
33. CONBOY, K. 2006. A Framework of agility in information systems development. Ph. D dissertation. University of Limerick, Limerick, Ireland.
34. CONNORS, D. T. 1992. Software development methodologies and traditional and modern information systems. Softw. Eng. Notes 17, 2, 43-49.
35. CRISPIN, L. AND HOUSE, T. 2003. Testing Extreme Programming. Pearson, Boston, MA.
36. CRONHOLM, S. AND GOLDKUHL, G. 1994. Meanings and motivates of method customization in CASE environments-observations and categorizations from an empirical study. In Proceedings of the 5th Workshop on the Next Generation of CASE Tools.
37. DALKEY, N. AND HELMER, O. 1963. An experimental application of the Delphi method to the use of experts. J. Institute Man. Sci. 9, 3, 458-467.
38. DAVIS, G. B. 1982. Strategies for information requirements determination. IBM Syst. J. 21, 1, 4-30.
39. DELBECQ, A. L., VAN DE VEN, A. H., ET AL. 1975. Group Techniques for Program Planning. Scott Foresman and Company, Glenview IL.
40. DEMARCO, T. 1982. Controlling Software Projects: Management Measurement and Estimation. Prenctice-Hall, Englewood Cliffs, NJ.
41. FITZGERALD, B. 1996. Formalised systems development methodologies: A critical perspective. Inform. Syst. J. 6, 1, 3-23.
42. FITZGERALD, B., HARTNETT, G., ET AL. 2006. Customising agile methods to software practices. Eur. J. Inform. Syst. 15, 2, 197-210.
43. FITZGERALD, B., RUSSO, N., ET AL. 2002. Information Systems Development: Methods in Action. McGraw-Hill, New York, NY.
44. FOWLER, M. AND HIGHSMITH, J. 2001. The agile manifesto. Softw. Develop. 9, 8, 28-32.
45. GLASS, R. 1991. Software Conflict: Essays on the Art and Science of Software Engineering. Yourdon Press, Prentice Hall, Englewood Cliffs, NJ.
46. GREMILLION, L. AND PYBURN, P. 1983. Breaking the systems development bottleneck. Harvard Busin. Rev. 61, 2, 130-137.
47. HARDY, C., THOMPSON, J., ET AL. 1995. The use, limitations and customization of structured systems development methods in the United Kingdom. Inform. Softw. Tech. 37, 9, 467-477.
48. HARMSEN, F. 1997. Situational method engineering. Ph. D. dissertation. Twente University, Enschede, Netherlands.
49. HARMSEN, F., BRINKKEMPER, S., ET AL. 1994. Situational method engineering for IS project approaches. In Methods and Associated Tools for the IS Life Cycle, A. Verrijn-Stuart and T. Olle, Eds. North-Holland, Elsevier Science, Amsterdam, The Netherlands, 169-194.
50. HENDERSON-SELLERS, B. AND SEROUR, M. 2005. Creating a dual-agility method: The value of method engineering. J. Datab. Manag. 16, 4, 1-23.
51. HIGHSMITH, J. 2004. Agile Project Management. Addison-Wesley, Reading, MA.
52. IIVARI, J. 1989. Amethodology forIS developmentas organizational change. In Syst. Development for Human Progress, H. Klein and K. Kumar, Eds. North-Holland, Amsterdam, The Netherlands, 197-217.
53. JENKINS, A., NAUMANN, J., ET AL. 1984. Empirical investigation of systems development practices and results. Inform. Man. 7, 1, 73-82.
54. JOHNSON, D. AND CARISTI, J. 2003. eXtreme programming and the software design course. In Extreme Programming Perspectives, M. Marchesi, G. Succi, D. Wells, and L. Williams, Eds. Addison Wesley, Reading, MA, 47-59.
55. JOHNSON, J. 1995. Chaos: The dollar drain of IT project failures. Appl. Develop. Trends 2, 1, 41-47.
56. KARLSSON, F. AND AGERFALK, P. 2004. Method configuration: Adapting to situational characteristics while creating reusable assets. Inform. Softw. Tech. 46, 9, 619-633.
57. KEIL, M., MANN, J., ET AL. 2000. Why software projects escalate: An empirical analysis and test of four theoretical models. MIS Quart. 24, 4, 631-664.
58. KIRCHER, M., JAIN, P., ET AL. 2001. Distributed extreme programming. In Proceedings of the Conference on XP2001-eXtreme Programming and Flexible Processes in Software Engineering.
59. KIRCHER, M. AND LEVINE, D. 2001. The XP of Tao: eXtreme programming of large opensource frameworks. In Extreme Programming Examined. Addison-Wesley, Reading, MA, 463-485.
60. KOCH, A. 2005. Agile Software Development: Evaluating the Methods for Your Organization. Artech House, Norwood, MA.
61. KUMAR, K. AND WELKE, R. J. 1992. Methodology engineering: A proposal for situation-specific methodology construction. In Challenges and Strategies for Research in Systems Development, W. Cotterman and J. Senn, Eds. John Wiley & Sons Ltd., New York, NY, 257-269.
62. LEHMAN, M. 1978. Why software projects fail. In Proceedings of the Infotech State of the Art Conference. Pergamon Press, New York, NY.
63. LINBERG, K. 1999. Software developer perceptions about software project failure: A case study. J. Syst. Softw. 4 9, 1, 177-192.
64. LINSTONE, H. AND TUROFF, M. 1975. Introduction. The Delphi Method: Techniques and Applications, H. Linstone and M. Turoff, Eds., Addison-Wesley, Reading, MA, 3-12.
65. MARTIN, R. 2003. Agile Software Development: Principles, Patterns and Practices. Prentice-Hall, Upper Saddle River, NJ.
66. MCBREEN, P. 2003. Questioning Extreme Programming. Addison-Wesley, Reading, MA.
67. MCCRACKEN, G. 1988. Qualitative Research: The Long Interview. Sage Publications, London, UK.
68. MCDOWELL, C., WERENER, L., ET AL. 2003. The impact of pair programming on student performance, perception and persistence. In Proceedings of the 25th International Conference on Software Engineering. Portland, OR.
69. MEYER, M. AND BOOKER, J. 2001. Eliciting and Analyzing Expert Judgment: A Practical Guide. Society for Industrial Mathematics, Boston, MA.
70. MILES, M. AND HUBERMAN, A. 1999. Qualitative Data Analysis. Sage, London, U. K.
71. MIRBEL, I. AND RALYTE, J. 2006. Situational method engineering: Combining assemble-based and roadmap-driven approaches. J. Requirement Engin. 11, 1, 58-78.
72. MOORE, C. 1987. Group Techniques for Idea Building. Sage Publications, London, U. K.
73. NAUMANN, J., DAVIS, G., ET AL. 1980. Determining information requirements: A contingency method for selection of a requirements assurance strategy. J. Syst. Softw. 1, 4, 273-281.
74. NECCO, C., GORDON, C., ET AL. 1987. Systems analysis and design: Current practices. MIS Quart. 11, 3, 461-476.
75. OFFENBEEK, M. AND VAN KOOPMAN, P. 1996. Scenarios for systems development: matching context and strategy. Behav. Inform. Tech. 15, 4, 250-265.
76. OPPENHEIM, A. 1992. Questionnaire Design, Interviewing and Attitude Measurement. Continuum, New York, NY.
77. POOLE, C. AND HUISMAN, J. 2001. Using extreme programming in a maintenance environment. IEEE Softw. 18, 6, 42-50.
78. POPPENDIECK, M. 2001. Lean programming. Softw. Develop. Mag. 9, 5, 71-75.
79. RASMUSSON, J. 2003. Introducing XP into greenfield projects: Lessons learned. IEEE Comput. 20, 3, 21-28.
80. ROBEY, D. AND KEIL, M. 2001. Blowing the whistle on troubled software projects. Comm. ACM 44, 4, 87-93.
81. ROLLAND, C. AND PRAKASH, N. 1996. A proposal for context-specific method engineering. In Method Engineering: Principles of Method Construction and Tool Support, S. Brinkkemper, K. Lyytinen, and R. Welke, Eds. Chapman & Hall, Atlanta, CA, 191-208.
82. RUSSO, N., WYNEKOOP, J., ET AL. 1995. The use and adaptation of system development methodologies. In Managing Information & Communications in a Changing Global Environment, M. Khosrowpour, Eds. Idea Group Publishing, Philadelphia, PA, 843-844.
83. SACKMAN, H. 1975. Delphi Critique. Heath and Co., Lexington, MA.
84. SCHWABER, C. AND FICHERA, R. 2005. Corporate IT leads the second wave of agile adoption. Forrester res. rep. Forrester Research, Cambridgr, MA.
85. SCHWABER, K. 1996. Controlled chaos: Living on the edge. Amer. Program. 9, 5, 10-16.
86. SCHWABER, K. AND BEEDLE, M. 2002. Agile Software Development with Scrum. Prentice-Hall, Upper Saddle River, NJ.
87. SOMMERVILLE, I., AND RANSOM, J. B. 2005. An industrial experiment in requirements engineering process assessment and improvement. ACM Trans. Softw. Eng. Methodol. 14, 1-33.
88. STAPLETON, J. 1997. DSDM: Dynamic Systems Development Method. Addison Wesley, Reading, MA.
89. STEPHENS, M. AND ROSENBERG, D. 2003. Extreme Programming Refactored. Apress, New York, NY.
90. STOTTS, D., WILLIAMS, L., ET AL. 2003. Virtual Teaming: Experiments and Experiences with Distributed Pair Programming. Extreme Programming/Agile Universe. Springer, New Orleans, L. A.
91. SULLIVAN, C. H. 1985. Systems planning in the information age. Sloan Busi. Rev. 26, 2, 3-11.
92. TAN, C. AND TEO, H. 2007. Training future software developers to acquire agile development skills. Comm. ACM 50, 12, 97-98.
93. TOLVANEN, J. AND LYYTINEN, K. 1993. Flexible method adaptation in CASE-the metamodeling approach. Scand. J. Inform. Syst. 5, 1, 51-77.
94. TRAUTH, E. AND O'CONNOR, B. 1991. A study of the interaction between information, technology and society. Information Systems Research: Contemporary Approaches and Emergent Traditions, H. Nissen, H. Klein, and R. Hirschheim, Eds., North Holland, Elsevier, Amsterdam, The Netherlands, 131-144.
95. TRUEX, D., BASKERVILLE, R., ET AL. 1999. Growing systems in emergent organizations. Comm. ACM 42, 8, 117-123.
96. UHL, N. 1983. Using Research for Strategic Planning. Jossey-Bass, San Francisco, CA.
97. VIJAYASARATHY, L. AND TURK, D. 2008. Agile software development: A survey of early adopters. J. Inform. Tech. Man. 19, 2, 1-8.
98. WAINER, M. 2003. Adaptations for Teaching Software Development with eXtreme Programming: An Experience Report. XP/Agile Universe, Springer.
99. WOOD-HARPER, A., ANTILL, L., ET AL. 1985. Information Systems Definition: The MultiView Approach. Blackwell Publishers, Oxford, U. K.
100. WYNEKOOP, J. L. AND RUSSO, N. L. 1995. Systems development methodologies: Unanswered questions. J. Inform. Tech. 10, 2, 65-73.
101. YIN, R. 2003. Case Study Research: Design and Methods. Sage Publications, Thousand Oaks, CA.