Email this article 
Open Access
Subscription or Fee Access
Adoption of Scrum Methodology in Agile Projects: Insights from India
Abstract
The fundamentals of agile software development address the improvement and management of software development practices within individual teams. They can support the earlier and quicker production of the code by dividing the product into small segments called iterations. The agile methods are well known for their focus on quality and higher morale of stakeholders. The agile software development improves the product usability when it is leveraged with the practice of frequently testing the user screens that is being developed by the agile team. The user experience designs, their needs and goals were monitored frequently when a technique such as scrum is being adopted. This paper contains a case study to empirically illustrate quality of a product by the usage and the adoption of the scrum technique with the experiences of the user team and the project team on a live software project. It also narrates how effective is the Agile methodology in handling the unstable or changing requirements throughout the software development life cycle.
Keywords
References
Sommerville, I., (2001), Software Engineering, Addison-Wesley Publishers Limited, USA.
ISACA, (2008), ‘Changing Business Needs and Unmet Expectations are Leading Causes to Technology Project Failures’ Available: http://www.isaca.org/Content/ContentGroups/News_Releases1/20082/ISACA_Study_Examines_Primary_Causes_of_Technology_Project_Failures.htm. [accessed 30/03/2010]
Palmer S.R. and Felsing J.M., (2002), A Practical Guide to Feature-Driven Development
Comptroller and Auditor General (CAG), Ireland, (Oct 2007), “eGovernment: Special Report”.
Beck, K., (1999), Extreme Programming Explained, Addison Wesley.
Cockburn, A., (2002), Agile Software Development, Pearson Education
Schwaber, K. and Beedle, M. (2001), Agile Software Development with Scrum, Prentice Hall, Edition
Chrissis, M. B., Konrad, M. and Shrum, S. (2004), CMMI – Guidelines for Process Integration and Product Improvement, Pearson Education, Inc., Boston, MA.
Escalona, M. J. and Koch, N., (2004), ‘Requirements Engineering for Web Applications – A Comparative Study’, Journal of Web Engineering, Vol. 2, No.3, p 193-212.
Haas, K. B., (May 2007), TIPS and TECHNIQUES: The Blending of Traditional and Agile Project Management, PM World Today, Vol. IX, Issue V.
Ambler, S., (2006), Agile Adoption Rate Survey: March 2006 [Online], Available: http://www.ambysoft.com/surveys/agileMarch2006.html [accessed 07/04/2010].
Ambler, S., (2008), Agile Adoption Rate Survey: February 2008 [Online], Available: http://www.ambysoft.com/surveys/agileFebruary2008.html#Downloads [accessed 30/4/2009].
Kilpatrick, J., (2003), Lean Principles [Online], Available: http://www.mep.org/textfiles/LeanPrinciples.pdf [accessed 30/3/2010].
Sutherland, J. and Schwaber, K , (2007), The Scrum Papers: Nuts, Bolts, and Origins of an Agile Process.
Poppendieck, T. and Poppendieck, M., (2006), Implementing Lean Software Development, Addison-Wesley.
Schwaber, K., (2008), What is Scrum? [Online], Available: http://www.controlchaos.com/about/ [accessed 27/3/2008].
Martin, R., (2004), ‘Best Practices in Scrum Project Management and XP Agile Software Development’, Object Mentor Inc.,
Pichler, R., (2007), Scrum Alliance, Being an Effective Product Owner
Scrum Alliance, (2008a), Scrum Artifacts [Online], Available: http://www.scrumalliance.org/view/scrum_ceremonies [accessed 4/5/2010].
Szalvay, V. (2007), ‘Glossary of Scrum Terms’, Scrum Alliance [Online], Available: http://www.scrumalliance.org/articles/39-glossary-of-scrum-terms#1115 [accessed 28/3/2010].
Cohn, M., (2008), ‘A Reusable Scrum Presentation’ [Online], Available: http://www.mountaingoatsoftware.com/scrum_a_presentation [accessed 20/2/2010].
Ambler, S., (2008c), The Agile Development Lifecycle (SDLC) [Online], Available: http://www.ambysoft.com/essays/agileLifecycle.html [accessed 10/5/2010].
Szalvay, S., (2006), Hierarchical Requirements and Scrum [Online], Available: http://danube.com/system/files/Hierarchical+Requirements+and+Scrum+blog_0.pdf [accessed 4/5/2010].
Patton, J., (2002). ‘Hitting the target: adding interaction design to agile software development’. Proceedings of Conference on Object Oriented Programming Systems Languages and Applications, Seattle, Washington, USA, pp. 1 – ff.
Hussain, Z., Lechner, M., Milchrahm, H., Shahzad, S., Slany, W., Umgeher, M. and Wolkerstorfer, P., (2008), ‘Agile User-Centered Design Applied to a Mobile Multimedia Streaming Application’, 4th Symposium of the WG HCIandUE of the Austrian Computer Society, Springer Berlin, Heidelberg, pp.313-330.
Ambler, S., (2007a), Scaling On-Site Customer, [Online], Available: http://www.ddj.com/architect/204801134?pgno=2 [accessed 9/5/2010].
Shriver, R., (2008), Qualities, User Stories and sad state of Scrum requirements [Online], Available: http://www.theagileengineer.com/public/Home/Entries/2008/10/12_Qualities,_User_Stories_and_sad_state_of_Scrum_requirements.html [accessed 10/5/2010]
Barry Boehm, Richard Turner, (Aug 2003), “Balancing Agility and Discipline: A guide for Perplexed”, Addison Wesley.
C. Labib, E. Hasanein, and O. Hegazy, (April 2009), Early development of graphical user interface (GUI) in agile methodologies (extended). Journal of Computational Methods in Sciences and Engineering, Volume 9, Issue 1, Netherlands.
Bin Xu (2009), “Towards High Quality Software Development with Extreme Programming methodology: Practices from real software projects, IEEE Xplore
Refbacks
- There are currently no refbacks.
This work is licensed under a Creative Commons Attribution 3.0 License.