Modeling Fault Detection Phenomenon in Multiple Sprints for Agile Software Environment

Prabhanjan Mishra (), A. K. Shrivastava (), P. K. Kapur () and Sunil K. Khatri ()
Additional contact information
Prabhanjan Mishra: Amity University
A. K. Shrivastava: Amity University
P. K. Kapur: Amity University
Sunil K. Khatri: Amity University

A chapter in Quality, IT and Business Operations, 2018, pp 251-263 from Springer

Abstract: Abstract The information technology industry has gone through a revolutionary change in the last two decades. In today’s fast changing business environment, the IT organizations have to be agile and responsive to cater to the needs of the customers. The objective is not just to deliver quickly but also to embrace the change without having any adverse impact on the project. The requirements of the end customers are fast changing and get evolved over a period of time as these are directly aligned with the market needs. This has led the organizations to adopt “Agile” approach based on “lean” principles over the conventional software development life cycle (SDLC) approach. In “Agile” framework, the customer works in collaboration with the project team in prioritizing the requirements. The implementation is done through “Scrum” methodology, having multiple “sprints,” and each sprint has a “working software” as a deliverable. This approach has substantially reduced the “time to market” as the customer can decide which features of the software they would like to be delivered on a priority basis. The release of sprints is similar to multi-releases of a software in which software is tested rigorously to detect the underlying faults at the end of each sprint and remaining number of fault of each sprint is taken forward for the next sprint. Hence to model the fault detection phenomenon and their trend in each sprint, software reliability growth modeling has been used. In the current work, we are using software reliability growth models (SRGMs) to find out the trend over the sprints that could ultimately define the overall quality of the software. Numerical illustration is mentioned at the end of the paper for model validation.

Keywords: Software reliability growth models (SRGMs); Agile framework; Scrum; Sprints; Modeling; Release; Testing; SDLC (search for similar items in EconPapers)
Date: 2018
References: Add references at CitEc
Citations: View citations in EconPapers (2)

There are no downloads for this item, see the EconPapers FAQ for hints about obtaining it.

Related works:
This item may be available elsewhere in EconPapers: Search for items with the same title.

Export reference: BibTeX RIS (EndNote, ProCite, RefMan) HTML/Text

Persistent link: https://EconPapers.repec.org/RePEc:spr:prbchp:978-981-10-5577-5_20

Ordering information: This item can be ordered from
http://www.springer.com/9789811055775

DOI: 10.1007/978-981-10-5577-5_20

Access Statistics for this chapter

More chapters in Springer Proceedings in Business and Economics from Springer
Bibliographic data for series maintained by Sonal Shukla () and Springer Nature Abstracting and Indexing ().