To do this we conducted a mixed-methods research study which comprised of interviews of 10 agile practitioners from New Zealand and Australia, a literature review, and an in-depth survey with the participation of 40 agile practitioners world-wide. We also wanted to know whether responding to changes is the only or a main reason for software teams to use agile in their projects. Requirements changes (RCs) are inevitable in any software development environment, and we wanted to acquire a holistic picture of how RCs occur and are handled in agile SE teams in practice. However, no study appears to have researched whether this is accurate in reality. During the development process, we also examined the extent of requirements volatility and discovered that the rate of volatility was high at the time of requirements specification completion and while functional specification reviews were conducted.Īgile processes are now widely practiced by software engineering (SE) teams, and the agile manifesto claims that agile methods support responding to changes well. Adopting an industrial case study approach, our findings reveal that the main causes of requirements volatility were changes in customer needs (or market demands), developers' increased understanding of the products, and changes in the organization policy. This taxonomy allows us to identify and trace the problems, reasons and sources of changes. We apply a causal analysis method on change request data to develop a taxonomy of change. ![]() We mainly focus on change analysis to identify and characterize the causes of requirements volatility. This increased understanding will improve the process of requirements change management. Investigating the factors that drive requirements change is an important prerequisite for understanding the nature of requirements volatility.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |