User Research

Topics: Agile software development, Waterfall model, Systems Development Life Cycle Pages: 29 (8807 words) Published: May 5, 2013
Association for Information Systems

AIS Electronic Library (AISeL)
UK Academy for Information Systems Conference Proceedings 2010 3-23-2010 UK Academy for Information Systems

University of Wales Institute Cardiff,

Hilary Berger
University of Wales Institute Cardiff,

Recommended Citation
Flouri, Kiriaki and Berger, Hilary, "AGILE DEVELOPMENT – SCRUM ADOPTED IN PRACTICE BUT NOT IN PRINCIPLE" (2010). UK Academy for Information Systems Conference Proceedings 2010. Paper 21.

This material is brought to you by the UK Academy for Information Systems at AIS Electronic Library (AISeL). It has been accepted for inclusion in UK Academy for Information Systems Conference Proceedings 2010 by an authorized administrator of AIS Electronic Library (AISeL). For more information, please contact

AGILE DEVELOPMENT – SCRUM ADOPTED IN PRACTICE BUT NOT IN PRINCIPLE Kiriaki Flouri Cardiff School of Management, University of Wales Institute Cardiff, Colchester Avenue, Cardiff, CF23 9XR, UK Email: Dr. Hilary Berger Cardiff School of Management, University of Wales Institute Cardiff, Colchester Avenue, Cardiff, CF23 9XR, UK Email: Abstract The move to agile software development methodologies has generated great enthusiasm. The emphasis on team-oriented development and reliance on people rather than predefined processes is transforming software development into a socio-technical process. Through the lens of a real-world project we examined the difficulties experienced when an IS development project shifted from a structured waterfall approach for upfront requirements gathering to a Scrum agile approach for the development activities. We specifically look at the agile values and principles of ‘people, working software, end-user involvement and responding to change’. Although the transition was successful in practice, in principle the project failed. The empirical case study evidences the characteristics involved and we put forward critical factors of the preparation of the environment (i.e. adequate Scrum training), effective communications (i.e. consensus on a standard working context and sufficient time for testing), optimal team structure (i.e. personalities) and effective team leadership to inform future development practice.

Keywords: Agile Methods, Scrum, People, Working Software, End-users, Change.



The shift from former traditional structured development approaches such as the Waterfall Model to agile software development methodologies is well documented. However whilst the move from the former static traditions to the more dynamic nature of agile development practices improved the discipline of systems development it did not resolve all the problems associated with the need to accommodate business uncertainty and the changing requirements of stakeholders/users (Elliott 1997; Graham 1989). Continued high rates of project overrun, over budget failures and systems that did not meet user requirements remained challenging (Boehm 1999; Coughlan and Macredie 2002; McConnell 1996). Consequently growth and change are recognized as intrinsic elements of IS development thus creating a demand for alternative more flexible development approaches able to respond to the increasingly

dynamic nature of evolving business environments – namely agile approaches (Elliott 1997; Martin 1991; Raffoni 2000).

A number of agile software development methodologies or lightweight methodologies have been developed since 1990s to embrace, rather than reject, high rates of change (Abrahamsson et al. 2003; Boehm 2002; Williams and Cockburn 2003). Some examples are Adaptive Software Development (ASD, Cockburn 2000), Dynamic Systems Development Method (DSDM, Stapleton 1997), eXtreme Programming (XP, Erickson...

References: Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J. (2002) Agile software Development Methods: Review and Analysis, Espoo VTT Publications 478 [Available URL:] [Accessed on: 15th March 2008]. Balijepally, V., Mahapatra, R. and Nerur, S. (2006) Assessing Personality Profiles of Software Developers in Agile Development Teams, Communications of AIS, Vol. 18, pp. 2-40. Beck, K., Grenning, J., Martin, C.R., Beedle, M., Highsmith, J. and Mellor, S. (2001) Manifesto for Agile Software Development, - 22 -
[Available URL:] [Accessed on: 30th September 2007]. Blumberg, B. and Cooper, D. R. and Schindler, P. S., (2005) Business Research methods, McGraw Hill Education, Berkshire. Boehm, B. (1999) Making RAD work for your Project, IEEE Computer, Vol. 3, pp. 113-117. Boehm, B. (2002) Get Ready for Agile Methods with Care [Available URL:] [Accessed on: 25th January 2007]. Boehm, B. and Turner, R. (2003) Using risk to balance agile and plan driven methods, IEEE Computer, Vol. 36(6), pp. 57-66. [Available URL:] [Accessed on: 13th October 2008]. Bono, J. E., Boles. T.L., Judge, T.A. and Lauver, K.J. (2002) The Role of Personality in Task and Relationship Conflict, Journal of Personality, Vol. 70(2), pp. 311-344. Cho, J. (2008) Issues and Challenges of Agile Software Development with Scrum, In Proceedings of 48th Annual IACIS International Conference, October 1-4, Savannah, Georgia, USA. [Available from:]. Cohn, M. (2004) User Stories Applied, Addison-Wesley Professional. Cockburn, A. (2000) Writing Effective Use Cases-The Crystal Collection for Software Professionals, Addison-Wesley, Reading, MA. Cockburn, A. and Highsmith, J. (2001) Agile software development: The business of innovation, IEEE Computer, Vol. 34(9), pp. 120–122. Cockburn, A. (2002) Agile software development, Addison-Wesley, Reading, MA. Cooper, D. R. and Schindler, P.S. (2006) Business Research Methods, (9th edn), McGraw-Hill, New York. Coughlan, J. and Macredie, R. D. (2002) Effective Communications in Requirements Elicitation: a Comparison of Methodologies, Requirements Engineering, Vol. 7(2), pp. 47-60. Damian, D. and Zowghi, D. (2003) Requirements Engineering Challenges in Multisite Software Development Organizations, Requirements Engineering, Vol. 8, pp. 149-160. Dyba, T. and Dingsøyr, T. (2008) Empirical studies of agile software development: A systematic review, Information and Software Technology, Vol. 50, pp. 833– 859. Elliott, E. (1997) Rapid Applications Development (RAD): an odyssey of information systems methods, tools and techniques. 4th Financial Information Systems Conference, Sheffield Hallam University, U.K. Erickson, J., Lyytinen, K. and Siau, K. (2005) Agile Modeling, Agile Software Development and Extreme Programming: The State of Research, Journal of Database Management, Vol. 16(4), pp. 88–100. Graham, D. R. (1989) Incremental Development: review of non-monolithic lifecycle development models, Information and Technology Software, Vol. 31, pp. 7-20. Highsmith, J. (2000) Retiring Lifecycles Dinosaurs, Software Testing & Quality Engineering, July/August, pp. 22-28. Highsmith, J. (2002) Agile Software Development Ecosystems, Addison-Wesley, Boston, MA. Highsmith, J. (2003) Cutter Consortium Reports: Agile Project Management: - 23 -
Principles and Tools, Cutter Consortium, Vol. 4(2), Arlington, MA. Iivari, J., Hirschheim, R. and Klein, H.K. (2000) A Dynamic Framework for Classifying Information Systems Development Methodologies and Approaches, Journal of Management Information Systems, Vol. 17(3), pp. 179-218. Kim, Y. (2007) Analyzing Scrum Agile Software Development with Development Process, Social Factor and Project Management Lenses, In Proceedings of the 13th Americas Conference of Information System (AMCIS-07). Koskela, J. (2003) Software configuration management in agile methods, Espoo VTT Publications. [Available URL: &type=pdf] [Accessed on: 23rd February 2008]. Klein, H.K. and Myers, M.D. (1999) A set of Principles for Conducting and Evaluating Interpretative Field Studies in IS, MIS Quarterly, Vol. 23(1), pp. 67-94. Kruchten, P. (2000) The Rational Unified Process: An Introduction, Addison-Wesley, Reading, MA. Leffingwell, D. (2007) Scaling Software Agility-Best Practices for Large Enterprises, Addison Wesley, Boston, MA. Lindstrom L. and Jeffries R. (2004), Extreme programming and agile software development methodologies, Information Systems Management, Vol. 21(3), pp. 41–61. Lindvall, M., Basili, VR., Boehm, B., Costa, P., Dangle, K., Shull, F., Tesoriero, R.,Williams, L., Zelkowitz, M.V. (2002) Empirical findings in agile methods Extreme Programming and Agile Methods—XP/Agile Universe 2002, Springer, Berlin. Mann, C. and F. Maurer (2005) A Case Study on the Impact of Scrum on Overtime and Customer Satisfaction, In Proceedings of XP/Agile Universe 2005, Denver Colorado, US. Martin, J. (1991) Rapid Application Development, New York: Macmillan. Martin, R. C. (2003). Agile software development: Principles, patterns, and practices. Upper Saddle River, NJ: Prentice Hall. McAvoy, J. and Butler, T. (2007) The impact of the Abilene Paradox on double-loop learning in an agile team, Information and Software Technology, Vol. 49, pp. 552-563. McConnell, S. (1996) Rapid Development – Taming Wild Software Schedules, Washington: Microsoft Press. McMahon, P. E. (2005) Extending Agile Methods: A Distributed Project and Organisational Improvement Perspective [Accessed on: 3rd February 2008] [Available ULR:]. Nerur, S., Radhakanta, M. and Mangalaraj, G. (2005) Challenges of Migrating to Agile Methodologies, Communications of the ACM, May2005, Vol. 48(5), pp. 73-78. Orr, K. (2002) CMM versus Agile Development: Religious Wars and Software Development, Agile Project Management Advisory Service, Vol. (3)7, pp. 29. Preece, J. Rogers, Y. Sharp, H. Benyon, D. Holland, S. and Carey, T. (1998) HumanComputer Interaction, England: Addison Wesley. Pressman, S.R. (2001) Software Engineering: A Practitioner’s Approach, (5th edn), - 24 -
McGraw-Hill, New York. Raffoni, M. (2000) Got a need for Speed, what you can learn from RAD, Harvard Management Update, Vol. 5(11), pp. 10. Robson, C. (2002) Real World Research, (2nd edn), Blackwell, Oxford. Sanders, M., Lewis, P. and Thornhill, A. (2007) Research Methods for Business Students, (4th edn), FT Prentice Hall, Harlow, England. Schwaber, K. and Beedle, M. (2002) Agile software development with Scrum, FT Prentice Hall, Upper Saddle River, NJ. Stazinger, J. W., Jackson, R. B. and Burd, S. D. (2005) Object-oriented analysis and design with unified process, Thomson Course- Technology, Boston. Stapleton, J. (1997) Dynamic Systems Development Method – The method in practice, Addison Wesley, Harlow, UK. Sutherland, J. and Schwaber, K. (2007) The Scrum Papers: Nuts, Bolts and Origins of an Agile method, [Available URL:] [Accessed on: 18th July 2008] Sutherland, J. Jacobson, C. and Johnson, K. (2007) Scrum and CMMI Level 5: A Magic Potion for Code Warriors!, in Agile 2007, Washington, D.C. Takeuchi H. and Nonaka, I. (1986) The New Product Development Game, Harvard Business Review, Vol. 64, pp.137-46. Vinekar, V., Slinkman, C. W. and Nerur, S. (2006) Can Agile and Traditional Systems Development Approaches Coexist? An Ambidextrous View, Information Systems Management, Summer 2006, Vol. 23(3), pp. 12, 31-42. Walsham, G. (2006) Doing interpretive research, European Journal of Information Systems, 15(3), 320-330. Williams, L. and Cockburn, A. (2003) Agile Software Development: it 's about Feedback and Change’, IEEE Computer, Vol. 36(6), pp. 39-43. [Available URL:] [Accessed on: 10th October 2006]
- 25 -
Continue Reading

Please join StudyMode to read the full document

You May Also Find These Documents Helpful

  • User Authentication Through Typing Patterns Research Paper
  • Casestudy of admin user Essay
  • Visual Studio 2010
  • The Architecture and Datasets of Docear’s Research Paper Recommender System
  • Calbaog City Samar Doctor's Clinic Research Paper
  • Toluene Diisocyanate (TDI) Market: Global Industry Analysis & Forecast (2013
  • 8 Steps in How to Write a Research Paper
  • Research Essay

Become a StudyMode Member

Sign Up - It's Free