Leveraging creativity in requirements elicitation within agile software development: A systematic literature review

Abstract

Agile approaches tend to focus solely on scoping and simplicity rather than on problem solving and discovery. This hampers the development of innovative solutions. Additionally, little has been said about how to capture and represent the real user needs. To fill this gap, some authors argue in favor of the application of "Creative thinking" for requirements elicitation within agile software development. This synergy between creativeness and agility has arisen as a new means of bringing innovation and flexibility to increasingly demanding software.The aim of the present study is therefore to employ a systematic review to investigate the state-of-the-art of those approaches that leverage creativity in requirements elicitation within Agile Software Development, as well as the benefits, limitations and strength of evidence of these approaches.The review was carried out by following the guidelines proposed by Dr. Kitchenham. The search strategy identified 1451 studies, 17 of which were eventually classified as primary studies. The selected studies contained 13 different and unique proposals. These approaches provide evidence that enhanced creativity in requirements elicitation can be successfully implemented in real software projects. We specifically observed that projects related to user interface development, such as those for mobile or web applica-

Agile elicitation of scalability requirements for open systems: A case study

“…According to Pacheco et al (2018), these techniques are still the most common. Pacheco et al (2018), Aldave et al (2019) describe more techniques like collaboration techniques (focus groups, workshops, and brainstorming), contextual techniques (combining unstructured interviews and prototyping), gamification, and storyboards. Using the ScrumScale model as a spanning object, we complement these elicitation techniques.…”

Enhanced Framework for Big Data Requirement Elicitation

“…The requirement elicitation for big data software applications using agile methodology is not easy and straightforward. A detailed requirement is required in the software development life cycle, but agile focuses on less documentation, neglecting quality requirements, difficulties with communication in distributed teams, and quick processing, which can lead to skipping necessary user requirements [5]. Customer satisfaction is the only evidence that requirements are complete and comprehensive, and agile methodology provides many ways to keep the customer involved.…”

“…Mind mapping provides the best practice in requirement election representation on the basis of its graphical concept, i.e., mapping the main ideas together to obtain the best value, producing an accurate and clear requirement representation while considering big data characteristics and quality attributes, which greatly aids in obtaining well-prioritized requirements. Nowadays, agile SCRUM methodology has gained popularity because of its properties, such as flexibility, which can handle the technical issues mentioned above, as it handles changes in requirements, customer involvement, and satisfaction, besides documenting the requirements in the product backlog [5]. Although agile is the commonly used methodology in big data projects because of its resilience in accepting new and changes in requirements during the implementation process, big data project needs more optimized methodologies to deal with the massive changes of requirements especially in big data project considering its characteristics.…”

Assessing Product Creativity in Computing Education: A Systematic Mapping Study

“…Bolden et al (2019) and Snyder et al (2019) provide overviews of the assessment of creativity in any discipline in K-12, not targeting specifically on computing education. Very few reviews are related to creativity in the context of computer science, analyzing approaches for leveraging creativity in agile requirements software engineering (Aldave et al, 2019) and individual creativity support systems (Wang and Nickerson, 2017). However, these reviews in the computing context typically do not focus on an educational perspective nor specifically on the product.…”