Abstract
In agile software development methodology, software product is developed through a few iterations and delivered incrementally. In spite of the known benefits of the agile methodology, yet issue still exists in developing high-quality software product using this methodology. Hence, quality assurance mechanism should be in place in agile development to ensure quality adherence to the software product. However, taking up quality assurance in agile software development is not an easy task as it has its own manifesto and principles that need to be met. Thus, this paper highlights the issues and challenges towards adopting quality assurance in agile development methodology. Particularly, in aniteration where we need to assure that the product increment meets the requirements as well as to decide the requirements for next increment and iteration planning. Subsequently, few measuresare identifiedconcerning the issues. The discussion in this paper is based on Scrum case, yet still relevant to other types of agile methodologies.
Highlights
Agile software development methodology focuses on frequent delivery through light and fast development cycle while adapting customers’ requirements changes
Quality assurance mechanism must be established in agile development methodology in order to ensure high-quality software product is produced
The quality assurance mechanism is needed to assure that the developed product increment meets the requirements, as well as to inform the requirements for the increment and iteration planning that might evolve.This will ensure that the quality is encountered earlier before the final product delivered
Summary
Agile software development methodology focuses on frequent delivery through light and fast development cycle while adapting customers’ requirements changes. Quality assurance mechanism must be established in agile development methodology in order to ensure high-quality software product is produced. Quality assurance in agile software development is not an easy task since the working software must be releasable and yet still open for frequent requirements changes. This paperdiscussesissues as well as measures that need to be considered in adopting software quality assurance in agile, Scrum methodology.Our work focuses in adopting quality assurance during the review process of product increment.
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
Free) 
Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a call
