Abstract
Agile methods fit well for software development teams in the requirements elicitation activities. It has brought challenges to organizations in adopting the existing traditional methods, as well as new ones. Design Thinking has been used as a requirements elicitation technique and immersion in the process areas, which brings the client closer to the software project team and enables the creation of better projects. With the use of data triangulation, this paper brings a literature review that collected the challenges in software requirements elicitation in agile methodologies and the use of Design Thinking. The result gave way to a case study in a Brazilian public organization project, via user workshop questionnaire with 20 items, applied during the study, in order to identify the practice of Design Thinking in this context. We propose here an overview of 13 studied challenges, from which eight presented strong evidence of contribution (stakeholders involvement, requirements definition and validation, schedule, planning, requirement details and prioritization, and interdependence), three presented partial evidence of contribution and two were not eligible for conclusions (non-functional requirements, use of artifacts, and change of requirements). The main output of this work is to present an analysis of the use of Design Thinking to see if it fits properly to be used as a means of solving the challenges of elicitation of software requirements when using agile methods.
Highlights
Proper requirements elicitation in a software project is considered one of the most important and difficult tasks during the software process
In our systematic literature review, we identified 12 challenges that organizations confronted within the elicitation of requirements in agile projects and 31 Design Thinking techniques: 13 techniques are related to the immersion phase, 10 techniques are related to the ideation phase and 8 techniques are related to the implementation phase
The goal of the evaluation approach was to evaluate whether the use of Design Thinking techniques can contribute positively to the challenges identified in the requirements elicitation, in projects developed with agile methodologies
Summary
Proper requirements elicitation in a software project is considered one of the most important and difficult tasks during the software process. The agile methodology has been popular since 2001 due to the valorization of teams members and the intense interaction among them, constant software deliveries, more effective stakeholder collaboration and an openness to receive changes from the users [3]. Agile methodologies emerged as an innovative proposal so that companies could deliver products expected by users on time and efficiently for the development team, due to the fact that software development processes should be extremely organized, wasting only a minimum of resources [14]. According to Fadel and Teixeira [14], in agile methodologies, at each iteration, a sub-project (components, functionalities or modules of the software) is created, and all steps of the software development process are realized: planning, requirements, coding and testing. The iterations last for a few weeks, which leads to quick results, mainly for users
Sign-in/Register to view highlights & summary Sign-in/Register to access full text options 
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 callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
