Agile Requirements Engineering: A systematic literature review

Nowadays, Agile Software Development (ASD) is used to cope with increasing complexity in system development. Hybrid development models, with the integration of User-Centered Design (UCD), are applied with the aim to deliver competitive products with a suitable User Experience (UX). Therefore, stakeholder and user involvement during Requirements Engineering (RE) are essential in order to establish a collaborative environment with constant feedback loops. The aim of this study is to capture the current state of the art of the literature related to Agile RE with focus on stakeholder and user involvement. In particular, we investigate what approaches exist to involve stakeholder in the process, which methodologies are commonly used to present the user perspective and how requirements management is been carried out. We conduct a Systematic Literature Review (SLR) with an extensive quality assessment of the included studies. We identified 27 relevant papers. After analyzing them in detail, we derive deep insights to the following aspects of Agile RE: stakeholder and user involvement, data gathering, user perspective, integrated methodologies, shared understanding, artifacts, documentation and Non-Functional Requirements (NFR). Agile RE is a complex research field with cross-functional influences. This study will contribute to the software development body of knowledge by assessing the involvement of stakeholder and user in Agile RE, providing methodologies that make ASD more human-centric and giving an overview of requirements management in ASD.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2015-71938-RED

The Effect of Organizational Structure on the Adoption of Agile Methodologies_A Case Study

This exploratory case study used observations and interviews to investigate how the structure of an organization impacts its ability to adopt agile software development methodologies. It also aimed to identify the agile practices that are perceived as helpful or unhelpful by the individuals practicing them. It examined an organization’s attempt to adopt agile methodologies for the first time in a new software product development project. Twelve employees from different teams working on this project participated in the study. . The participants were asked about their perception of the agile process. They were also asked to identify the various teams with which they regularly interact and to provide examples of the helpful and unhelpful patterns of behavior they exhibit. The findings suggest that the structure of the organization was a major limiting factor that affected its ability to adopt agile methodologies. Agile practices rely on the level of flexibility that an organization can demonstrate. However, the organization attempted to adopt agile practices without redefining the project members’ roles, work processes, or departmental affiliations. Participants perceived many aspects of the agile methods negatively, and various symptoms of a misfit between the existing organizational structure and the requirements of agile methods were observed, including poor communication and multiple conflicts between the different project teams, which caused the project to go over time and over budget. Furthermore, it was observed that the teams struggled to follow the agile practices and found various ways to alter and work around them to fit the existing structure, rather than adhering to them and welcoming the new practices. Several potential areas for future research are identified, including: using longitudinal case studies to examine organizations and the relationships between their members before and after adopting agile methodologies, in order to identify and attribute any observed behavioral patterns to the appropriate cause; examining organizations in which the structure was altered to accommodate agile methodologies; and examining how organizations define the roles of highly specialized employees who possess very specific abilities and must be shared across different development projects

Agile thinking in motion graphics practice and its potential for design education

Motion Graphics is relatively new subject and its methodologies are still being developed. There are useful lessons to be learnt from the practice in early cinema from the 1890's to the 1930's where Agile thinking was used by a number of practitioners including Fritz Lang. Recent studies in MA Motion Graphics have accessed some of this thinking incorporating them in a series of Motion Graphic tests and experiments culminating in a two minute animation “1896 Olympic Marathon”. This paper demonstrates how the project and its design methodology can contribute new knowledge for the practice and teaching of this relatively new and expanding area of Motion Graphic Design. This would be not only invaluable to the International community of Motion Graphic practitioners, Educators and Researchers in their development of this maturing field. But also to the broader Multidisciplinary disciplines within Design Education. These methodologies have been arrived at by accessing the work of creative and reflective practice as defined by Carol Grey and Julian Marlin in Visualizing Research (2004) and reflective practice as defined by Donald Schon (1983). Central to the investigation has been the approach of Agile thinking from the methodology of "Bricolage" by Levi Strauss "The Savage Mind" (1966)