Share This Article:

The Success Factors of Running Scrum: A Qualitative Perspective

Abstract Full-Text HTML XML Download Download as PDF (Size:571KB) PP. 367-374
DOI: 10.4236/jsea.2012.56043    7,598 Downloads   12,945 Views   Citations
Author(s)    Leave a comment

ABSTRACT

Scrum—Agile programming—is getting more attention in Software Engineering practices. Many software projects began with small and were not certain about the requirements until projects have completed; this makes Scrum more appropriate than other development methodologies. This paper reintroduced Scrum from qualitative perspective by applying ethnography and in-depth interview to two different types of project teams to articulate what the success factors are for running Scrum framework. It clearly demonstrated how qualitative research could help in disclosing the essence of facts during the Scrum adaptation in depth. It also articulated how these successful factors mutually affect to one another from System Dynamics perspective and to give further recommendations to Scrum teams and those who tend to apply Scrum development methodology.

Conflicts of Interest

The authors declare no conflicts of interest.

Cite this paper

R. C. Lee, "The Success Factors of Running Scrum: A Qualitative Perspective," Journal of Software Engineering and Applications, Vol. 5 No. 6, 2012, pp. 367-374. doi: 10.4236/jsea.2012.56043.

References

[1] A. Gopal, T. Mukhopadhyay and M. S. Krishnan, “The Role of Software Processes and Communication in Offshore Software Development,” Communications of the ACM, Vol. 45, No. 4, 2002, pp. 193-200. doi:10.1145/505248.506008
[2] M. Aoyama, “New Age of Software Development: How Component-Based Software Engineering Changes the Way of Software Development,” 1998 International Workshop on CBSE, Kyoto, 25-26 April 1998, pp. 124-128.
[3] http://assets.scrumtraininginstitute.com/downloads/1/scrumprimer121.pdf
[4] J. Y. Yeh, C. C. Wei, C. S. Wei and D. F. Lei, “The Impact of Team Personality Balance on Project Performance,” African Journal of Business Management, Vol. 6, No. 4, 2012, pp. 1674-1684.
[5] G. Cugola and C. Ghezzi, “Software Processes: A Retrospective and a Path to the Future,” Software Process: Improvement and Practice, Vol. 4, No. 3, 1998, pp. 101-123. doi:10.1002/(SICI)1099-1670(199809)4:3<101::AID-SPIP103>3.0.CO;2-K
[6] http://www.fhi360.org/en/RH/Pubs/booksReports/QRM_datacoll.htm
[7] J. W. Forrester, “System Dynamics, Systems Thinking, and Soft OR,” System Dynamics Review, Vol. 10, No. 2-3, 1994, pp. 245-256. doi:10.1002/sdr.4260100211
[8] P. Abrahamsson, O. Salo, J. Ronkainen and J. Warsta, “Agile Software Development Methods: Review and Analysis,” VTT Publications, Espoo, 2002.
[9] M. C. Davis, D. J. Leach and C. W. Clegg, “The Physical Environment of the Office: Contemporary and Emerging Issues,” International Review of Industrial and Organizational Psychology, Vol. 26, 2011, pp. 193-237.
[10] V. U. Druskat and J. V. Wheeler, “Managing from the Boundary: The Effective Leadership of Self-Managing Work Teams,” Academy of Management Journal, Vol. 46, No. 4, 2003, p. 435. doi:10.2307/30040637
[11] Y. L. Chen, “Analysis of the Agile Deployment,” Master’s Thesis, University of Gothenburg, Gothenburg, 2010.
[12] N. B. Moe, T. Dingsoyr and T. Dyba, “Overcoming Barriers to Self-Management in Software Teams,” Software, Vol. 26, No. 6, 2009, pp. 20-26. doi:10.1109/MS.2009.182
[13] C. Keith, “An Agile Retrospective,” Game Developer Conference, February 2008.
[14] A. Cockburn, “Crystal Clear: A Human-Powered Methodology for Small Teams,” Addison-Wesley, Boston, 2005.
[15] M. Ikonen, P. Kettunen, N. Oza and P. Abrahamsson, “Exploring the Sources of Waste in Kanban Software Development Projects,” 36th Euromicro Conference on Software Engineering and Advanced Applications, Lille, 1-3 September 2010, pp. 376-381.
[16] L. D. Rola, “Kanban for Small Software Projects,” Project Background Report, The University of Manchester, Manchester, 2011.
[17] A. E. Roger, F. N. Marcel and A. C. Lopez, “Business Process Requirement Engineering,” International Journal on Computer Science and Engineering, Vol. 2, No. 9, 2010, pp. 2890-2899.
[18] M. R. Haas, “Knowledge Gathering, Team Capabilities, and Project Performance in Challenging Work Environments,” Management Science, Vol. 52, No. 8, 2006, pp. 1170-1184. doi:10.1287/mnsc.1060.0530
[19] E. Fossey, C. Harvey, F. McDermott and L. Davidson, “Understanding and Evaluating Qualitative Research,” Australian & New Zealand Journal of Psychiatry, Vol. 36, No. 6, 2002, pp. 717-732. doi:10.1046/j.1440-1614.2002.01100.x
[20] M. Luz, D. Gazineu and M. Teofilo, “Challenges on Adopting Scrum for Distributed Teams in Home Office Environments,” World Academy of Science, Engineering and Technology, No. 59, 2009, pp. 308-311.
[21] J. Highsmith and A. Cockburn, “Agile Software Development: The Business of Innovation,” Computer, Vol. 34, No. 9, 2001, pp. 120-127. doi:10.1109/2.947100
[22] G. Lee and W. Xia, “Toward Agile: An Integrated Analysis of Quantitative and Qualitative Field Data on Software Development Agility,” MIS Quarterly, Vol. 34, No. 1, 2010, pp. 87-114.
[23] J. D. Sterman, “System Dynamics Modeling,” California Management Review, Vol. 43, No. 4, 2001, pp. 8-25.
[24] J. Grenning, “Planning Poker or How to avoid Analysis Paralysis while Release Planning,” Hawthorn Woods: Renaissance Software Consulting, Vol. 3, 2002.
[25] P. Runeson and M. Host, “Guidelines for Conducting and Reporting Case Study Research in Software Engineering,” Empirical Software Engineering, Vol. 14, No. 2, 2009, pp. 131-164. doi:10.1007/s10664-008-9102-8

  
comments powered by Disqus

Copyright © 2018 by authors and Scientific Research Publishing Inc.

Creative Commons License

This work and the related PDF file are licensed under a Creative Commons Attribution 4.0 International License.