Requirement Understanding

From the recent literature review, it is evident that existing agile methodology lacks the method to evaluate the requirement understanding of agile team members for a given set of requirement chosen for agile software development. Hence, there is a need to introduce a requirement understanding check to ensure every agile team member follows the given requirement clearly without any ambiguity. To fill this existing gap, this research paper proposes to extend the usage of story cards to evaluate the understanding of the given requirement and to highlight any challenges and risks in the early stage of requirement understanding under agile software development methodology, if any. This paper primarily focuses to introduce a robust requirement understanding evaluation process in agile methodology. The research results were found to be motivating and were analyzed by comparing the data-points using time-series for performing agile query analysis, agile team velocity analysis and agile team involvement analysis for two agile teams where one team delivered the sprint output using agile traditional method while another team opted for proposed approach. A considerable decrease of 33.07% was observed in the number of queried raised and a significant increase of 26.36% in agile velocity was observed for agile sprint under proposed approach when compared to agile traditional approach. Also, a significant shift from 40%-80% team involvement under traditional agile method was uplifted to 80%-90% team involvement under proposed approach.