Preview

User Research

Powerful Essays
Open Document
Open Document
8807 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
User Research
Association for Information Systems

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

AGILE DEVELOPMENT – SCRUM ADOPTED IN PRACTICE BUT NOT IN PRINCIPLE
Kiriaki Flouri
University of Wales Institute Cardiff, kflouri@uwic.ac.uk

Hilary Berger
University of Wales Institute Cardiff, Hberger@uwic.ac.uk

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. http://aisel.aisnet.org/ukais2010/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 elibrary@aisnet.org.

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: kflouri@uwic.ac.uk Dr. Hilary Berger Cardiff School of Management, University of Wales Institute Cardiff, Colchester Avenue, Cardiff, CF23 9XR, UK Email: Hberger@uwic.ac.uk 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



References: Abrahamsson, P., Salo, O., Ronkainen, J. and Warsta, J. (2002) Agile software Development Methods: Review and Analysis, Espoo VTT Publications 478 [Available URL: http://www.pss-europe.com/P478.pdf] [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: http://agilemanifesto.org/] [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: http://www2.umassd.edu/swpi/xp/papers/r1064.pdf] [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: http://www.acq.osd.mil/se/as/publications/IEEE%20Software%206-03.pdf] [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: http://www.iacis.org/iis/2008_iis/pdf/S2008_950.pdf]. 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: http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.106.4156&rep=rep1 &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: http://www.sstc-online.org/Proceedings/2005/PDFFiles/PEM786pap.pdf]. 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: http://scrumtraininginstitute.com/home/stream_download/scrumpapers] [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: http://csdl2.computer.org] [Accessed on: 10th October 2006] - 25 -

You May Also Find These Documents Helpful

  • Powerful Essays

    Jharna Software is a software company located in India that was established in 1992, with a focus on IT services for the banking and finance sector. Its offerings include e-commerce solutions, networking solutions, offshore services, applications development, enterprise resource planning, customer relationship management (CRM), e-CRM and business process outsourcing. Jharna received awards from the Indian government for performance in exports and does well in the market. The founders believe that their high-quality offerings at low price points is the key to their success, helped by their focus on maintaining a highly-skilled work force which they built by focusing on employee benefits and training. However, intense pressure from competitors has caused Jharna’s management to feel the need to improve on current practices.…

    • 1504 Words
    • 7 Pages
    Powerful Essays
  • Best Essays

    The Software Development Life Cycle (SDLC) gives very definable goals regardless of the methodology used; the development process will have a planning and a testing phase whether it is Waterfall or Agile. At Smith Consulting (SC), projects begin with a project planning phase when SC selects team leaders and assigns jobs to team members based on their particular strengths. Then SC locks project requirements into an open-ended Agile process…

    • 3816 Words
    • 16 Pages
    Best Essays
  • Good Essays

    Nt1310 Unit 1 Assignment 1

    • 1252 Words
    • 6 Pages

    Motivated by recognition of software development as fluid, unpredictable, and dynamic ● Three key principles ● Adaptive rather than predictive ● Emphasize people rather than roles ● Self-adaptive…

    • 1252 Words
    • 6 Pages
    Good Essays
  • Powerful Essays

    This article was downloaded by: [Vlerick Leuven Gent Management School] On: 13 November 2012, At: 03:37 Publisher: Routledge Informa Ltd Registered in England and Wales Registered Number: 1072954 Registered office: Mortimer House, 37-41 Mortimer Street, London W1T 3JH, UK…

    • 9619 Words
    • 39 Pages
    Powerful Essays
  • Good Essays

    Project Plan

    • 9315 Words
    • 38 Pages

    Rafamanickam, D. (2005). Successful Project Management Using Agile Methodology. Journal of the Quality Assurance Institute. Vol. 19 Issue 3, p15-18. Retrieved June 2, 2006 from EBSCOhost database, University of Phoenix Online Library Collection.…

    • 9315 Words
    • 38 Pages
    Good Essays
  • Best Essays

    The Scrum approach has been developed gaming for managing the systems development process. It is an empirical approach applying the ideas of industrial process control theory to gaming development resulting in an approach that reintroduces the ideas of flexibility, adaptability and productivity (Schwaber & Beedle 2002). It does not define any specific software development techniques for the implementation phase. Scrum concentrates on how the team members should function in order to produce the system flexibly in a constantly changing environment.…

    • 3180 Words
    • 13 Pages
    Best Essays
  • Better Essays

    Gayatr, G. and Pammi, K. 2013. Agile User Stories - Scrum Alliance. [online] Available at: https://www.scrumalliance.org/community/articles/2013/september/agile-user-stories [Accessed: 1 Mar 2014].…

    • 2238 Words
    • 9 Pages
    Better Essays
  • Powerful Essays

    Agile Methodology

    • 2132 Words
    • 9 Pages

    Agile methodology is an approach to the project management which help to respond to the unpredictability of building software through incremental, iterative work cadences, known as sprints. This methodology was developed to deal with situation where the waterfall model fails. The biggest drawback of waterfall model is that it assumes that every requirement of the project can be identified before any design or coding occurs. This may always be applicable for the development of a automobile on an assembly line, in which each piece is added in sequential phases. However it may or may not be applicable for software development. For example, for a BAU (Business as Usual) projects where the software is already in use for a long time, waterfall model is the best method to implement any changes requests because amount of uncertainly is very less compared to developing a new product. However for developing brand new software, waterfall model is not an ideal choice as the amount of uncertainty in terms of requirement and user quality expectation. It might be the case that end product is not exactly what user has expected due to mismatch of requirement understanding between user and developer. It might also be the case that a team might have built the software it was asked to build, but, in the time it took to create, business realities have changed so dramatically that the product is irrelevant. In that scenario, a company has spent time and money to create software that no one wants.…

    • 2132 Words
    • 9 Pages
    Powerful Essays
  • Good Essays

    Genesis Health Care

    • 1900 Words
    • 8 Pages

    An agile approach to managing the process will create a platform for growth, starting with employee satisfaction. Figure 1 illustrates the simplicity of communication SCRUM has a small-scale basis (Becheru, 2014). It is very easy to discuss ideas for improvement using an agile method because everyone is on the same level collaborating with each other.…

    • 1900 Words
    • 8 Pages
    Good Essays
  • Good Essays

    Agile Estimation Paper

    • 497 Words
    • 2 Pages

    Thank you for working with AA Consulting this past month and allowing us the opportunity to work with your IT Development Team observing their current Agile practices. Throughout this week we had the privilege to sit in on Agile Ceremonies across several teams. When we were first engaged to provide support for Agile Development, the area of concern for management and product owners was the realm of estimations. As such, the area that our consulting team placed focus on was during the Backlog Grooming and Estimation sessions. Our goal was to understand why for the past 6 months development teams have provided inconsistent estimations, derailing project timelines and costing Company X almost 175% of their predicted development costs for the quarter.…

    • 497 Words
    • 2 Pages
    Good Essays
  • Good Essays

    Jokes

    • 568 Words
    • 3 Pages

    * Agile Scrum can work with any technology/ programming language but is particularly useful for fast moving web 2.0 or new media projects.…

    • 568 Words
    • 3 Pages
    Good Essays
  • Powerful Essays

    V Model vs Agile Methodology

    • 2703 Words
    • 11 Pages

    This document discusses in an interpretive way the commonly used Software Development Lifecycle Models and their implications to Software Project Management. Their application, advantages and disadvantages are discussed.…

    • 2703 Words
    • 11 Pages
    Powerful Essays
  • Good Essays

    Week 7 Discussion

    • 960 Words
    • 4 Pages

    Wysocki,R.K .(2012) Effective Project Management: traditional, agile, extreme. 6th edn. Indianapolis: Wiley Publishing, Pp. 311-320…

    • 960 Words
    • 4 Pages
    Good Essays
  • Powerful Essays

    Scrum methodology is regarded as one of the best technique among agile methodologies. It is most suitable for development of complicated projects, which are characterized with rapidly changing environment (requirements and other factors). The features of this methodology, all of which are important, make this technique successful. One of the features is that, the process is iterative, which means that products are realized at the end of each sprint/ iteration, or a cycle; this means that a revised version of a sprint would be incremental. This feature is important since it helps in achievement of small project components, which would be completed within a short period (mostly ranging from one week to one month). Each component or a unit is allocated to a team, which has to come up with the required product before the next step is approved for iteration (Per and Bruce 2006).…

    • 1792 Words
    • 8 Pages
    Powerful Essays
  • Powerful Essays

    The agile software engineering movement had a number of key aims: rapid response to change was favoured over just following a plan; working with customers was favoured over simple contract negotiation; working software was favoured over partially-working software with complex documentation; and finally, individualism was favoured over the use of individuals as simple steps in a process. Also, agile software engineering sought to ensure the continued and rapid delivery of changes and new ideas would impress upon the customer that the engineers were able to react to constantly changing situations. Meanwhile, it was also considered important to allow for constant changes, including changes at the very last minute, just as the product was ready to be unveiled. Finally, it was felt that the process had become almost more important than the outcome, so agile…

    • 1885 Words
    • 8 Pages
    Powerful Essays