Identifying Agile Requirements Engineering Patterns in Industry

Agile Software Development (ASD) is gaining in popularity in today´s business world. Industry is adopting agile methodologies both to accelerate value delivery and to enhance the ability to deal with changing requirements. However, ASD has a great impact on how Requirements Engineering (RE) is carried out in agile environments. The integration of Human-Centered Design (HCD) plays an important role due to the focus on user and stakeholder involvement. To this end, we aim to introduce agile RE patterns as main objective of this paper. On the one hand, we will describe our pattern mining process based on empirical research in literature and industry. On the other hand, we will discuss our results and provide two examples of agile RE patterns. In sum, the pattern mining process identifies 41 agile RE patterns. The accumulated knowledge will be shared by means of a web application.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2016-76956-C3-2-RMinisterio de Economía y Competitividad TIN2015-71938-RED

Enterprise Experience into the Integration of Human-Centered Design and Kanban

he integration of Human-Centered Design (HCD) and Agile Software Development (ASD) promises the development of competitive products comprising a good User Experience (UX). This study has investigated the integration of HCD and Kanban with the aim to gain industrial experiences in a real world context. A case study showed that requirements flow into the development process in a structured manner by adding a design board. To this end, the transparency concerning recurring requirements increased. We contribute to the body of knowledge of software development by providing practical insights into Human-Centered Agile Development (HCAD). On one hand, it is shown that the integration of HCD and Kanban leads to a product with a good UX and makes the development process more human-centered. On the other hand, we conclude that a cross-functional collaboration speeds up product development.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2015-71938-RED

Bridging the Gap Between Research and Practice: The Agile Research Network

We report an action research-oriented approach to investigating agile project management methods which aims to bridge the gap between academic research and agile practice. We have set up a research network of academics from two universities, through which we run focussed project-based research into agile methods. Organisations are invited to suggest an ‘agile challenge’ and we work closely with them to investigate how challenge affects them. Our approach is both academic and practical. We use appropriate research methods such as interviews, observation and discussion to clarify and explore the nature of the challenge. We then undertake a detailed literature review to identify practical approaches that may be appropriate for adoption, and report our findings. If the organisation introduces new practices or approaches as a result of our work, we conduct an academic evaluation. Alternatively, if we uncover an under-researched area, we propose undertaking some basic research. As befits the topic, we work iteratively and incrementally and produce regular outputs. In this paper we introduce our approach, overview research methods used in the agile research literature, describe our research model, outline a case study, and discuss the advantages and disadvantages of our approach. We discuss the importance of producing outputs that are accessible to practitioners as well as researchers. Findings suggest that by investigating the challenges that organisations propose, we uncover problems that are of real relevance to the agile community and obtain rich insights into the facilitators and barriers that organisations face when using agile methods. Additionally, we find that practitioners are interested in research results as long as publications are relevant to their needs and are written accessibly. We are satisfied with the basic structure of our approach, but we anticipate that the method will evolve as we continue to work with collaborators

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

Requirements engineering related usability techniques adopted in agile development processes

Over the last decade there has been a growing interest in the integration of agile software development process (ASDP) and user-centred design (UCD). However, there are no papers that study which usability techniques related to requirements engineering are being adopted in the ASDP, and there are no formalized proposals for their adoption. Objective: Identify which techniques related to requirements engineering activities are being adopted in the ASDP and determine how they are being adopted. Method: We have conducted a systematic mapping study (SMS) to retrieve the literature reporting the application of usability techniques in the ASDP. We analysed these techniques using a catalogue of techniques compiled by software engineering researchers. We then determined the manner in which the techniques that are being used in the ASDP were adopted. Results: The agile community is very much interested in adopting usability techniques. The most used techniques are Personas, contextual inquiry and prototyping. Conclusions: This research offers an overview of the adoption of usability techniques related to requirements engineering in ASDPs and reports how they are being adopted. We found that some of the techniques are being adapted for adoption.This research was funded by the Spanish Ministry of Education, Culture and Sports FLEXOR and “Realizando Experimentos en la Industria del Software: Comprensión del Paso de Laboratorio a la Realidad” projects (TIN2014-52129-R and TIN2014-60490-P, respectively) and the eMadrid-CM “Investigación y Desarrollo de Tecnologías Educativas en la Comunidad de Madrid” project (S2013/ICE-2715

Achieving Usability: Looking for Connections between User-Centred Design Practices and Resultant Usability Metrics in Agile Software Development

This article searches for correlations between the practices of usability professionals from software development teams and the resulting usability of the system they are working on. After reviewing the literature of the past decade, we can conclude that most researchers try to achieve better usability with process proposals, but measurements focus on perceived usability. The level of involvement of users in the requirements capture phase is unclear. There is a trend to reduce costs of usability engineering, either by choosing more lightweight and informal methods or by trying to substitute user involvement. Looking at decade's worth of 452 articles about "agile AND usability" in Scopus, we selected 133 which deal with the integration of usability, UX and User Centred Design practices and Agile development

Agile Design Process with User-Centered Design and User Experience in Web Interfaces: A Systematic Literature Review

In the search for faster software development techniquesthat consider user’s needs, agile methods are gettingspace in the corporate scenario, as well as in scientific research.However, integrating agile software development with usercentereddesign (UCD) and user experience (UX) is a challengingtask. In this way, we systematically reviewed the literature until2017 to identify and understand how UX can be considered inagile development, particularly for graphical interfaces of webapplications. The search was performed in the ACM, IEEE,Science Direct, and Springer databases. We found a total of 815studies, of which 13 met the eligibility criteria. This research isimportant for evidencing the information acquired and used tomap how agile methods can consider the stakeholders, activities,and techniques that directly imply the way the products aredeveloped to meet the user’s expectations. There are many agilemethods, each with its advantages and disadvantages, but weconclude that the methods that integrate better with UX or UCDare Scrum and XP

An agile information-architecture-driven approach for the development of user-centered interactive software

This is the author's version of the work. It is posted here for your personal use. Not for redistribution. The definitive Version of Record was published in Interacción '15: Proceedings of the XVI International Conference on Human Computer Interaction, http://dx.doi.org/10.1145/2829875.2829919.For the most part, Information Architecture processes include sets of activities and techniques to be carried out by the development team to create interactive applications effectively, involving usability concerns at every development step. In fact, plenty of process models have already been proposed to bridge the gap between User-Centered Development and Information Architecture, empowering the development team to build usable applications successfully. However, the combination of User- Centered Development and Information Architecture paradigms sometimes results in cumbersome process models containing lots of phases and activities to be considered, which increases the cycle time to have partial and validated software increments readily. As less effort has been devoted to speed up the usable Information Architecture development, the aim of this paper is to address such problem. To do so, we present Scrum-UIA, an agile and usable development process driven by the Information Architecture. This process is intended to develop web applications by splitting up responsibilities and tasks, and decreasing the time to perform technical activities, in order to readily obtain usable software increments.This work has been supported by the funding projects «eMadrid», granted by the Madrid Research Council (project code S2013/ICE-2715) and «Flexor», granted by the Spanish Government (project code TIN2014-52129-R)

Artifacts for Agile User-Centered Design: A Systematic Mapping

Abstract—The integration of Agile and User-Centered Design methods is a fundamental condition to improve the quality of software products. However, one of the main problems faced to establish this integration on a day-to-day basis is how to improve communication among the invariably distinct involved teams. We believe that the artifacts involved in the development process could be used to support and increase teams’ communication. To better understand this scenario, we performed a systematic mapping study on artifacts and their role in the communication between Agile and User-Centered Design fields. Through the analysis of 56 papers dealing with this specific topic, we present the artifacts used for communication in these approaches and software development events when they are used. The analyzed studies reinforced our beliefs about the importance of artifacts to improve teams’ communication