IScrum: An Improved Scrum Process Model

Full Text (PDF, 655KB), PP.16-24

Views: 0 Downloads: 0

Author(s)

Sara Ashraf 1,* Shabib Aftab 1

1. IScrum: An Improved Scrum Process Model

* Corresponding author.

DOI: https://doi.org/10.5815/ijmecs.2017.08.03

Received: 27 May 2017 / Revised: 6 Jun. 2017 / Accepted: 18 Jun. 2017 / Published: 8 Aug. 2017

Index Terms

Scrum, Improved Scrum, Tailored Scrum, Customized Scrum, Agile Model, Software Process Improvement

Abstract

Resolving a wide domain of issues and offering a variety of benefits to software engineering, makes the Agile process models attractive for researchers. Scrum has been recognized as one of the most promising and successfully adopted agile process models at software industry. The reason behind vast recognition is its contribution towards increased productivity, improved collaboration, quick response to fluctuating market needs and faster delivery of quality product. Though Scrum performs better for small projects but there are certain challenges that practitioners encounter while implementing it. Experts have made some efforts to adapt the Scrum in a way that could remove those drawbacks and limitations, however, no single effort addresses all the issues. This paper is intended to present a tailored version of Scrum aimed at improving documentation, team’s performance, and visibility of work, testing, and maintenance. The proposed model involves adapting and innovating the traditional Scrum practices and roles to overcome the problems while preserving the integrity and simplicity of the model.

Cite This Paper

Sara Ashraf, Shabib Aftab, "IScrum: An Improved Scrum Process Model", International Journal of Modern Education and Computer Science(IJMECS), Vol.9, No.8, pp.16-24, 2017. DOI:10.5815/ijmecs.2017.08.03

Reference

[1]S. Sharma, and N. Hasteer, "A comprehensive study on state of Scrum development," In Computing, Communication and Automation (ICCCA), 2016 International Conference on, pp. 867-872, IEEE, April 2016.
[2]M. Larusdottir, J. Gulliksen, & A. Cajander, “A license to kill–Improving UCSD in Agile development,” Journal of Systems and Software, vol. 123, pp. 214-222. 2017.
[3]R. K. Gupta, P. Manikreddy, & K. C. Arya, “Pragmatic Scrum Transformation: Challenges, Practices & Impacts During the Journey A case study in a multi-location legacy software product development team,” In Proceedings of the 10th Innovations in Software Engineering Conference pp. 147-156, ACM, Feb 2017.
[4]C. G. von Wangenheim, R. Savi, and A. F. Borgatto, "SCRUMIA—An educational game for teaching SCRUM in computing courses," Journal of Systems and Software, vol. 86, pp. 2675-2687, 2013
[5]M. M. Jha, R. M. F. Vilardell, & J. Narayan, “Scaling Agile Scrum Software Development: Providing Agility and Quality to Platform Development by Reducing Time to Market,” In Global Software Engineering (ICGSE), 2016 IEEE 11th International Conference on, pp. 84-88, IEEE, August 2016.
[6]J. S. Park, P. E. McMahon, & B. Myburgh, “Scrum powered by essence,” ACM SIGSOFT Software Engineering Notes, vol. 41, pp. 1-8, 2016.
[7]N. R. Darwish, & S. Megahed, “Requirements Engineering in Scrum Framework,” Requirements Engineering, vol. 149, 2016.
[8]C. Matthies, T. Kowark, K. Richly, M. Uflacker, and H. Plattner, “ScrumLint: identifying violations of agile practices using development artifacts,” In Cooperative and Human Aspects of Software Engineering (CHASE), 2016 IEEE/ACM, pp. 40-43, May 2016.
[9]N. R. Darwish, “Enhancements In Scum Framework Using Extreme Programming Practices,” International Journal of Intelligent Computing and Information Sciences (IJICIS), Ain Shams University, vol. 14, pp.53-67, 2014
[10]W. Singhto, & N. Denwattana, “An experience in blending the traditional and Agile methodologies to assist in a small software development project,” In Computer Science and Software Engineering (JCSSE), 2016 13th International Joint Conference on IEEE, pp. 1-5, July 2016.
[11]B. Schär, S. Jüngling, & B. Thönssen, “Towards an Agile Requirements Engineering Process Combining HERMES 5 and SCRUM,” In Enterprise Systems (ES), 2015 International Conference on IEEE, pp. 98-109, October 2015.
[12]R. Mokhtar, N. H. Jaafar, N. F. Tahar, S. A. Sukiman, A. Aris, and N. F. Abu Bakar, "An integrated document management system for managing self programme accreditation using Scrum approach," in Technology Management and Emerging Technologies (ISTMET), 2014 International Symposium on, pp. 102-106, 2014
[13]Savoine, M. Maria, V. F. Rocha, C. A. C. Bezerra, A. M. C. de Araújo, and J. K. M. Matias, “A Synchronous Agile Framework Proposal Combining Scrum and TDD,” ICSEA, pp.350, 2016
[14]S. Tirumala, S. Ali, B. G. Anjan, “A Hybrid Agile model using SCRUM and Feature Driven Development,” International Journal of Computer Applications vol. 156 pp. 1-5, 2016.
[15]T. Khalane and M. Tanner, "Software quality assurance in Scrum: The need for concrete guidance on SQA strategies in meeting user expectations," in Adaptive Science and Technology (ICAST), 2013 International Conference on, pp. 1-6. 2013.
[16]C. Orlowski, I. Bach-Dabrowska, P. Kaplanski, and W. Wysocki, "Hybrid Fuzzy-ontological Project Framework of a Team Work Simulation System Embedded System,” in International Conference on Information Technology, Procedia Computer Science, vol. 35, pp. 1175-1184, 2014.
[17]M. Tanveer, “Agile for large scale projects—A hybrid approach,” In Software Engineering Conference (NSEC), 2015 National IEEE, pp. 14-18, December 2015,
[18]R. Y. Takahira, L. R. Laraia, F. A. Dias, A. S. Yu, P. T. Nascimento, and A. S. Camargo, "Scrum and Embedded Software development for the automotive industry," in Management of Engineering & Technology (PICMET), 2014 Portland International Conference on, pp. 2664-2672, 2014.
[19]R. E. Maria, Jr, L.A. Rodrigues, and N. A. Pinto, “ScrumS: a model for safe agile development,” In Proceedings of the 7th International Conference on Management of computational and collective intElligence in Digital EcoSystems ACM, pp. 43-47, October 2015.
[20]U. Iqbal, and A. Javed, “Review-Scrum (R-Scrum) Introduction of Model Driven Architecture (MDA) In Agile Methodology,” International Journal of Technology Enhancements and Emerging Engineering Research, vol. 3, pp. 296-302, 2014.
[21]K. Petersen, & C. Wohlin, “A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case,” Journal of Systems and Software, vol. 82 no. 9, pp. 1479-1490, 2009.
[22]A. Cockburn, & J. Highsmith, “Agile software development, the people factor,” Computer, vol. 34 no. 11, pp. 131-133, 2001.
[23]A. Cockburn, “Agile Software Development,” Boston, MA, USA: Addison-Wesley Longman Publishing Co., Inc., 2002.
[24]P. Abrahamsson, J. Warsta, M. T. Siponen, and J. Ronkainen, “New directions on agile methods: A comparative analysis,” in Proceedings of the 25th International Conference on Software Engineering, ser. ICSE ’03. Washington, DC, USA: IEEE Computer Society, pp. 244–254, 2003.
[25]V. Szalvay, "An introduction to agile software development," Danube technologies, pp. 1-9, 2004.
[26]D. Mougouei, N. F. M. Sani, & M. M. Almasi, "S-Scrum: a secure methodology for agile development of web services," World of Computer Science and Information Technology Journal (WCSIT), vol. 3, no. 1, pp. 15-19, 2013.
[27]S. Alliance, “The 2015 State of Scrum Report,” Download unter www.Scrumalliance.org/why-Scrum/state-of-Scrumreport/2015-state-of-Scrum 2015. [Accessed: 05 01 2017]
[28]I. Ghani, Z. Azham, and S. R. Jeong, “Integrating Software Security into Agile-Scrum Method,” TIIS, vol. 8, pp. 646-663, 2014.
[29]K. Schwaber, “Agile project management with Scrum,” Microsoft press, 2004
[30]P. Deemer, G. Benefield, C. Larman and B. Vodde, “The Scrum primer V 1.2,” Scrum Alliance, http://www.brianidavidson.com/agile/docs/Scrumprimer121.pdf. [Accessed: 05 01 2017]
[31]P. Bootla, O. Rojanapornpun, and Mongkolnam, P., “Necessary skills and attitudes for development team members in Scrum: Thai experts' and practitioners’ perspectives,” In Computer Science and Software Engineering (JCSSE), 2015 12th International Joint Conference on pp. 184-189, IEEE. July 2015.
[32]C. D. O. Melo, V. Santos, E. Katayama, H. Corbucci, R. Prikladnicki, A. Goldman, and F. Kon, “The evolution of agile software development in Brazil,” Journal of the Brazilian Computer Society, vol. 19, no. 4, pp. 523-552, 2013.
[33]M. O. Ahmad, P. Kuvaja, M. Oivo, and J. Markkula, “Transition of software maintenance teams from Scrum to Kanban,” In System Sciences (HICSS), 2016 49th Hawaii International Conference on pp. 5427-5436, IEEE. 2016, January.
[34]J. López-Martínez, R. Juárez-Ramírez, C. Huertas, S. Jiménez, and C. Guerra-García, “Problems in the Adoption of Agile-Scrum Methodologies: A Systematic Literature Review,” In Software Engineering Research and Innovation (CONISOFT), 2016 4th International Conference in, pp. 141-148, IEEE, April,2016.
[35]S. Alliance, “The state of Scrum: benchmarks and guidelines,” F. L. Orlando, D. Kim. 2013.
[36]Mann, C. and Maurer, F., “A case study on the impact of Scrum on overtime and customer satisfaction,” In Agile Conference, 2005, Proceedings IEEE, pp. 70-79, July, 2005.
[37]F. Ghafoor, I. A. Shah, & N. Rashid, "Issues in Adopting Agile Methodologies in Global and Local Software Development: A Systematic Literature Review Protocol with Preliminary Results." International Journal of Computer Applications, vol. 160, no. 7, 2017.
[38]Kapitsaki, M. Georgia and M. Christou, "Where is Scrum in the current Agile world?," In Evaluation of Novel Approaches to Software Engineering (ENASE), IEEE, International Conference on, pp. 1-8, 2014.
[39]H. Iqbal, M. F. Khan, "Assimilation of Usability Engineering and User-Centered Design using Agile Software Development Approach,” IJMECS, vol.6, no.10, pp. 23-28, 2014.
[40]R. Noor, M. F. Khan, "Defect Management in Agile Software Development," IJMECS, vol.6, no.3, pp.55-60, 2014.
[41]F. Anwer, S. Aftab, S. S. M. Shah, and U. Waheed, “Comparative Analysis of Two Popular Agile Process Models: Extreme Programming and Scrum,” International Journal of Computer Science and Telecommunications, vol. 8, no. 2, March 2017.