Scrum: An Agile Software Development Process and Metrics


  • Rajani Dixit School of Computers, IPS Academy, Indore, Madhya Pradesh, India.
  • Brij Bhushan Mewar University, Mewar, Rajasthan, India.



Agile, Process Model, Scrum, Scrum Metrics


In a traditional software development process such as the Waterfall Model, works best in a stable environment. But, it is not flexible when it comes to change. There is a gap in the interaction between the users and the development team which leads to incomplete and misunderstood specification. Because of this, the end product is sometimes a surprise to users and this gap accelerates incorrect development of the software product. Once requirements are frozen there is no scope of accepting changes. There is a need for a framework which holds the solution for all these situations. With this premise, the agile development methodology came into existence. Scrum, an agile approach supports continuous collaboration among the customer, team members, and other stakeholders. Its time-boxed approach and continuous feedback from the product owner ensures the development of working product with essential features at all the time. This paper explains the agile software development approach, its proclamation and different frameworks of agile approach. Further illustrate most widely used framework: Scrum. This research paper covers the implementation and application of Scrum. It focuses on why Scrum is preferred over the Waterfall Model with the help of some survey results and later a discussion on some Scrum Metrics which will be helpful and accounting for the best Scrum Practices in achieving goals set by the software development team, the product owner and the customers. The outcome of this study shows that Scrum Metrics is critical and highly valuable for successful product development. The quantitative insight that these metrics provide for the Scrum Team, Product Owner and Stakeholders is necessary for achieving strong project dynamics and optimal results.


Download data is not yet available.


[1] M. Kramer, “Best practices in systems development lifecycle: An analyses based on the waterfall model”, Review of Business & Finance Studies, vol. 9, no. 1, pp. 77-84, 2018.
[2] J. Yu, “Research process on software development model”, IOP Conference Series: Materials Science and Engineering, 394, 2018.
[3] M. Kumara and E. Rashid, “An efficient software development life cycle model for developing software project”, International Journal of Education and Management Engineering, vol. 8, no. 6, pp. 59-68, 2018.
[4] R. Srikrishna, “The current state of outsourcing relationship: the Watermelon Effect”, 2015. [Online]. Available:
[5] C. Weisert, “Waterfall Methodology: there’s no such things”, 2003. [Online]. Available:
[6] C. Ziegler, “Android: A Visual History”, 2011 [Online]. Available:
[7] A. Ahmed, S. Ahmad, N. Ehsan et al., “Agile Software Development: Impact on Productivity and Quality”, IEEE ICMIT, 2010.
[8] J. A. Livermore, “Factors that impact implementing an Agile Software Development Methodology”, IEEE SoutheastCon, pp. 85-85, 2007.
[9] Beck et. al, “Lifecycle starts here: Manifesto for Agile Software Development”, 2001. [Online] Available:
[10] A. Qumer and B. Henderson-Seller, “ An evaluation of the degree of agility in six methods and its applicability for method engineering”, Elsevier Information and Software Technology, vol. 50, no. 4, pp. 20-29, 2008.
[11] D. West, M. Gilpin, T. Grant and A. Anderson, “Water-Scrum-Fall is the reality of agile for most organizations todays” Technical Report Forrester Research Inc., 2011.
[12] J. Sutherland, “Why waterfall doesn’t Scale, 2017. [Online]. Available:’t-scale/.
[13] K. Schwaber, “Scrum development process,” Proceedings of the 10th Annual ACM Conference on Object-Oriented Programming Systems, Languages and Applications OOPSLA, Texas, USA, pp.117-134, 1995.
[14] K. Schwaber and J. Sutherland, “The definitive guide to Scrum: The rules of the game, 2013. [Online]. Available:
[15] S. S. Sinha, “Does Scum Live up to its Hype?”, 2017. [Online]. Available:
[16] M. Cohn, “Agile Succeeds Three Times More Often Than Waterfall”, 2012. [Online] Available:
[17] J. Kisielnicki and M. A. Misiak, “Effectiveness of agile compared to waterfall implementation methods in IT projects: Analysis based on business intelligence projects”, Foundation of Management, vol. 9, 2017.
[18] M. Passivaara and B. Behm, C. Lassenius et al, “Large-scale agile transformation at Ericsson: a case study,” Empir Software Eng, 23:2550, 2018.
[19] E. Kilu, F. Milani, E. Scott and D. Pfahl, “Agile software process improvement by learning from financial and fintech companies: lhv bank case study”, Software Quality: The Complexity and Challenges of Software Engineering and Software Quality in the Cloud. SWQD, Lecture Notes in Business Information Processing, vol 338. Springer, Cham, 2019.
[20] E. Qi, H. Bi, X. Bi, “Study on agile software development based on scrum method,” Proceeding of the 24th International Conference on Industrial Engineering and Engineering Management, Springer, Singapore, 2018.
[21] D. Winkler, F. Rinker and P. Kieseberg, “Towards a flexible and secure round-tri-engineering process for production systems engineering with agile practices,” Software Quality: The Complexity and Challenges of Software Engineering and Software Quality in the Cloud. SWQD, Lecture Notes in Business Information Processing., vol 338. Springer, Cham, 2019.




How to Cite

Rajani Dixit, & Brij Bhushan. (2019). Scrum: An Agile Software Development Process and Metrics. Journal on Today’s Ideas - Tomorrow’s Technologies, 7(1), 73–87.