Examining customer focus in IT project management: Findings from Irish and Norwegian case studies

Scandinavian Journal of Information Systems

Volumn 23, Issue 2, 2011, Pages 29-58

  Lohan, Garry ^a   Conboy, Kieran ^a,b   Lang, Michael ^a  

^a NATIONAL UNIVERSITY OF IRELAND   (Ireland)

^b UNIVERSITY OF NEW SOUTH WALES   (Australia)

Author keywords

Agile project management; Agile systems development; Customer focus

Indexed keywords

EID: 84869157968     PISSN: 09050167     EISSN: 19010990     Source Type: Journal    
DOI: None     Document Type: Article

References (87)

1. Abrahamsson, P., Conboy, K., and Wang, X., (2009). Lots done, more to do: The current state of agile systems development research. European Journal of Information Systems, (18:4): 281-284.
2. Agile Alliance. (2001). Principles behind the Agile Manifesto. Retrieved July 14, 2010, from http://www.agilemanifesto.org/principles.html
3. Ahire, L. S., Golhar, Y. D., and Waller, A. M., (1996). Development and validation of TQM implementation constructs. Decision Sciences, (27:1): 23-56.
4. Albert, T. C., Goes, P. B., and Gupta, A., (2004). GIST: A model for design and management of content and interactivity of customer-centric websites. MIS Quarterly, (28:2): 161-182.
5. Ambler, S. W. (2007). Survey says. Agile has crossed the chasm. Dr Dobb's Journal, 32(8). Retrieved from http://www.drdobbs.com/architect-and-design/200001986
6. Appiah-Adu, K., and Singh, S., (1998). Customer orientation and performance: a study of SMEs. Management Decision, (36:6): 383-394.
7. Baldrige. (2010). Criteria for Performance Excellence. Retrieved 6th November, 2010, from http://www.baldrige.nist.gov/PDF_files/2009_2010_Business_Nonprofit_Criteria.pdf
8. Balka, E., (2010). Broadening discussion about participatory design: A reply to Kyng. Scandinavian Journal of Information Systems, (22:1): 77-84.
9. Barki, H., and Hartwick, J., (1994). Measuring user participation, user involvement and user attitude. Mis Quarterly, (18:1): 59-82.
10. Baskerville, R., and Pries-Heje, J., (2004). Short cycle time systems development. Information Systems Journal, (14:3): 237-264.
11. Beath, C. M., and Orlikowski, W. J., (1994). The contradictory structure of systems development methodologies: Deconstructing the IS-User relationship in information engineering. Information Systems Research, (5:4): 350-377.
12. Beck, K., and Andres, C., (2005). Extreme Programming Explained:Embrace Change, (2nd Edition ed.), Boston, MA., Addison-Wesley.
13. Benbasat, I., Goldstein, D. K., and Mead, M., (1987). The case research strategy in studies of information systems. MIS Quarterly, (11:3): 369-386.
14. Bragge, J., and Merisalo-Rantanen, H., (2009). Engineering e-collaboration processes to obtain innovative end-user feedback on advanced web-based information systems. Journal of the Association for Information Systems, (10:3): 196-220.
15. Cao, L., Mohan, K., Xu, P., and Ramesh, B., (2009). A framework for adapting agile development methodologies. European Journal of Information Systems, (18:4): 332-343.
16. Cao, L., and Ramesh, B., (2008). Agile requirements engineering practices: An empirical study. IEEE Software, (25:1): 60-67.
17. Chamberlain, S., Sharp, H., and Maiden, N., Towards a framework for integrating agile development and user-centred design. P. Abrahamsson, M. Marchesi and G. Succi, (eds.), Extreme Programming and Agile Processes in Software Engineering: 7th International Conference, XP Springer Berlin, Oulu, Finland, 2006, pp. 143-153.
18. Collins, (2005). Collins English Dictionary, Glasgow, HarperCollins.
19. Coltman, T., (2007). Why build a customer relationship management capability? The Journal of Strategic Information Systems, (16:3): 301-320.
20. Conboy, K., (2009). Agility from first principles: Reconstructing the concept of agility in information systems development. Information Systems Research, (20:3): 329-354.
21. Day, G. S., (2003). Creating a superior customer-relating capability. MIT Sloan Management Review, (44:3): 77-82.
22. Deshpande, R., Farley, J. U., and Jr., F. E. W., (1993). Corporate culture, customer orientation, and innovativeness in Japanese firms: A quadrad analysis. Journal of Marketing, (57:1): 23-37.
23. Dieste, O., Juristo, N., and Shull, F., (2008). Understanding the customer: What do we know about requirements elicitation? IEEE Software, (25:2): 11-13.
24. Drucker, P., (1954). The Practice of Management., New York:, HarperCollins.
25. Dybå, T., and Dingsøyr, T., (2008). Empirical studies of agile software development: A systematic review. Information and Software Technology, (50:9-10): 833-859.
26. EFQM. (2010). European Foundation for Quality Model. Retrieved 6th November, 2010, from http://tinyurl.com/6ejweg9.
27. Fitzgerald, B., Hartnett, G., and Conboy, K., (2006). Customising agile methods to software practices at Intel Shannon. European Journal of Information Systems, (15:2): 200-213.
28. Fundin, A. P., and Bergman, B. L. S., (2003). Exploring the customer feedback process. Measuring Business Excellence, (7:2): 55-65.
29. Grimstad, S., Jørgensen, M., and Moløkken-Østvold, K., (2006). Software effort estimation terminology: The tower of Babel. Information and Software Technology, (48:4): 302-310.
30. Gulati, R., (2007). Silo busting. Harvard Business Review, (85:5): 98-108.
31. Gulati, R., and Oldroyd, J. B., (2005). The quest for customer focus. Harvard Business Review, (83:4): 92-101.
32. Hanssen, G. K., and Fægri, T. E. (2006). Agile customer engagement: a longitudinal qualitative case study. G.H. Travassos, J.C. Maldonado and C. Wohlin (eds.), Proceedings of the 2006 ACM/IEEE international symposium on Empirical software engineering, ACM, Rio de Janeiro, Brazil, 2006, 164-173.
33. Highsmith, J., (2004). Agile Project Management, Boston, MA, Addison-Wesley.
34. Hope, J., and Fraser, R., (2003). Beyond Budgeting: How Managers can Break Free from the Annual Performance Trap, Boston, Mass, Harvard Business School Press.
35. Issac, G., Chandrasekharan, R., and Anantharaman, R. N., (2004). A conceptual framework for total quality management in software development organizations. Total Quality Management & Business Excellence, (15:3): 307-344.
36. Ives, B., and Olson, M. M., (1984). User involvement and MIS success: A review of research. Management Science, (30:5): 586-603.
37. Jokela, T., and Abrahamsson, P., (2004). Usability assessment of an extreme programming project: Close co-operation with the customer does not equal to good usability, in: Product Focused Software Process Improvement, F. Bomarius and H. Iida (eds.), Berlin, Springer-Verlag, 393-407.
38. Jwo, J.-S., and Cheng, Y. C., (2010). Pseudo software: A mediating instrument for modeling software requirements. Journal of Systems and Software, (83:4): 599-608.
39. Kankanhalli, A., Tan, B. C. Y., and Kwok-Kee, W., (2005). Contributing knowledge to electronic knowledge repositories: An empirical investigation. MIS Quarterly, (29:1): 113-143.
40. Kautz, K., Customer and User Involvement in Agile Software Development. P. Abrahamsson, M. Marchesi and F. Maurer, (eds.), XP2009, Springer, Pula, Sardinia, Italy, 2009.
41. Keil, M., and Carmel, E., (1995). Customer-developer links in software development. Communications of the Acm, (38:5): 33-44.
42. Kohli, A. K., and Jaworski, B. J., (1990). Market orientation:The construct, research propositions. Journal of Marketing, (54:2): 1-18.
43. Korkala, M., Pikkarainen, M., and Conboy, K., Distributed Agile Development: A Case Study of Customer Communication Challenges. P. Abrahamsson, M. Marchesi and F. Maurer, (eds.), XP2009, Springer, Pula, Sardinia, Italy, 2009.
44. Kumar, V., Venkatesan, R., and Reinartz, W., (2008). Performance implications of adopting a customer-focused sales campaign. Journal of Marketing, (72:5): 50-68.
45. Kyng, M., (2010). Bridging the gap between politics and techniques: On the next practices of participatory design. Scandinavian Journal of Information Systems, (22:1): 49-68.
46. Lee, G., and Xia, W., (2005). The ability of information systems development project teams to respond to business and technology changes: A study of flexibility measures. European Journal of Information Systems, (14:1): 75-92.
47. Lees, J. D., (1987). Successful development of small business information systems. Journal of Systems Management, (38:8): 32-39.
48. Liang, T.-P., and Tanniru, M., (2006). Special section: Customer-centric information systems. Journal of Management Information Systems, (23:3): 9-15.
49. Lin, W. T., and Shao, B. B. M., (2000). The relationship between user participation and system success: a simultaneous contingency approach. Information & Management, (37:6): 283-295.
50. Lindvall, M., Muthig, D., Dagnino, A., Wallin, C., Stupperich, M., Kiefer, D., May, J., and Kahkonen, T., (2004). Agile software development in large organizations. Computer, (37:12): 26-34.
51. Maiden, N., and Jones, S., (2010). Agile requirements: Can we have our cake and eat it too? IEEE Software, (27:3): 87-88.
52. Mann, C., and Maurer, F., A case study on the impact of Scrum on overtime and customer satisfaction, ADC 05, IEEE Computer Society, Denver, 2005. Martin, A., Biddle, R., and Noble, J., The XP customer team: A Grounded Theory, Agile Conference, 2009, 24-28 Aug. 2009, 2009, pp. 57-64.
53. Miles, M., and Huberman, A., (1994). Qualitative Data Analysis: An Expanded Sourcebook, (2nd Edition ed.), London, Sage.
54. Misra, S. C., Kumar, V., and Kumar, U., (2009). Identifying some important success factors in adopting agile software development practices. The Journal of Systems and Software, (82:11): 1869-1890.
55. Moe, N. B., Dingsoyr, T., and Dyba, T., (2010). A teamwork model for understanding an agile team: A case study of a Scrum project. Information and Software Technology, (52:5): 480-491.
56. Mohr-Jackson, I., (1991). Broadening the market orientation: An added focus on internal customers. Human Resource Management, (30:4): 455-467.
57. Molokken-Ostvold, K., and Furulund, K. M., The relationship between customer collaboration and software project overruns, AGILE 2007, 2007, pp. 72-83.
58. Narver, J. C., and Slater, S. F., (1990). The effect of a market orientation on business profitability. Journal of Marketing, (54:4): 20-35.
59. Neill, C. J., and Laplante, P. A., (2003). Requirements engineering: The state of the practice. IEEE Software, (20:6): 40-45.
60. OED. (2011). Focus Definition. Retrieved 3 January, 2011, from http://www.oed.com/view/ Entry/72350
61. Ovaska, P., Rossi, M., and Smolander, K., (2005). Filtering, negotiating and shifting in the understanding of information system requirements. Scandinavian Journal of Information Systems, (17:1): 31-66.
62. Parzinger, M. J., and Nath, R., (2000). A study of the relationships between total quality management implementation factors and software quality. Total Quality Management, (11:3): 353-371.
63. Petter, S., Straub, D., and Rai, A., (2007). Specifying formative constructs in information systems research. Mis Quarterly, (31:4): 623-656.
64. Pikkarainen, M., Haikara, J., Salo, O., Abrahamsson, P., and Still, J., (2008). The impact of agile practices on communication in software development. Empirical Software Engineering, (13:3): 303-337.
65. Ravichandran, T., and Rai, A., (1999). Total quality management in information systems development: Key constructs and relationships. Journal of Management Information Systems, (16:3): 119-155.
66. Rubin, H., and Rubin, I., (2005). Qualitative Interviewing: The Art of Hearing Data, Thousand Oaks, CA, Sage.
67. Sampson, S. E., (1996). Ramifications of monitoring service quality through passively solicited customer feedback. Decision Sciences, (27:4): 601-622.
68. Sampson, S. E., (1998). Gathering customer feedback via the internet: Instruments and prospects. Industrial Management + Data Systems, (98:2): 71-82.
69. Schwaber, K., (2004). Agile Project Management with Scrum, Redmond, WA., Microsoft Press.
70. Schwaber, K., and Beedle, M., (2002). Agile software development with scrum, Upper Saddle River, NJ, Prentice Hall.
71. Seybold, P. B., (2001). Get inside the lives of your customers. Harvard Business Review, (79:5): 80-89.
72. Shah, D., Rust, R. T., Parasuraman, A., Staelin, R., and Day, G. S., (2006). The path to customer centricity. Journal of Service Research, (9:2): 113-124.
73. Shalloway, A., Beaver, G., and Trott, J. R., (2009). Lean-Agile Software Development, Upper Saddle River, NJ., Addison-Wesley.
74. Silverman, D., (2005). Doing Qualitative Research, (2nd Edition ed.), London, Sage.
75. Slaughter, S. A., Levine, L., Ramesh, B., Pries-Heje, J., and Baskerville, R., (2006). Aligning software processes with strategy. MIS Quarterly, (30:4): 891-918.
76. Sousa, R., (2003). Linking quality management to manufacturing strategy: an empirical investigation of customer focus practices. Journal of Operations Management, (21:1): 1-18.
77. Srivastava, A., Bartol, K. M., and Locke, E. A., (2006). Empowering leadership in management teams: Effects on knowledge sharing, efficacy, and performance. Academy of Management Journal, (49:6): 1239-1251.
78. Stake, R., (1995). The Art of Case Study Research, Thousand Oaks, CA, Sage.
79. Stylianou, A. C., Kumar, R. L., and Khouja, M. J., (1997). A total quality management-based systems development process. The DATA BASE for Advances in Information Systems, (28:3): 59-71.
80. Svensson, H., and Host, M., Views from an organization on how agile development affects its collaboration with a software development team, Proceedings of the 9th European conference on software maintenance and reengineering (CSMR), Bomarius, F., and Komi-Sirviö, S. Manchester, UK, 2005, pp. 256-264.
81. Tiwana, A., and Keil, M., (2006). Functionality risk in information systems development: An empirical investigation. Ieee Transactions on Engineering Management, (53:3): 412-425.
82. Version-One. (2009). State of Agile Survey, fourth anual survey. Retrieved 2nd November, 2010, from http://tinyurl.com/72b2lpk.
83. Wagner, C., and Majchrzak, A., (2007). Enabling customer-centricity using Wikis and the Wiki way. Journal of Management Information Systems, (23:3): 17-43.
84. Wengraf, T., (2001). Qualitative Research Interviewing, London, Sage.
85. Yin, K., Robert., (2003). Case Study Research: Design and Methods, Thousand Oaks, California, Sage.
86. Yin, K. R., (2009). Case Study Research: Design and Methods, (4th ed.), London, Sage Publications.
87. Zultner, R. E., (1993). TQM for technical teams. Communications of the Acm, (36:10): 79-91.