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

The Contemporary Understanding of User Experience in Practice

User Experience (UX) has been a buzzword in agile literature in recent years. However, often UX remains as a vague concept and it may be hard to understand the very nature of it in the context of agile software development. This paper explores the multifaceted UX literature, emphasizes the multi-dimensional nature of the concept and organizes the current state-of-the-art knowledge. As a starting point to better understand the contemporary meaning of UX assigned by practitioners, we selected four UX blogs and performed an analysis using a framework derived from the literature review. The preliminary results show that the practitioners more often focus on interaction between product and user and view UX from design perspective predominantly. While the economical perspective receives little attention in literature, it is evident in practitioners writings. Our study opens up a promising line of request of the contemporary meaning of UX in practice.Comment: 8 pages, 1 figure, 3 table

SensorCloud: Towards the Interdisciplinary Development of a Trustworthy Platform for Globally Interconnected Sensors and Actuators

Although Cloud Computing promises to lower IT costs and increase users' productivity in everyday life, the unattractive aspect of this new technology is that the user no longer owns all the devices which process personal data. To lower scepticism, the project SensorCloud investigates techniques to understand and compensate these adoption barriers in a scenario consisting of cloud applications that utilize sensors and actuators placed in private places. This work provides an interdisciplinary overview of the social and technical core research challenges for the trustworthy integration of sensor and actuator devices with the Cloud Computing paradigm. Most importantly, these challenges include i) ease of development, ii) security and privacy, and iii) social dimensions of a cloud-based system which integrates into private life. When these challenges are tackled in the development of future cloud systems, the attractiveness of new use cases in a sensor-enabled world will considerably be increased for users who currently do not trust the Cloud.Comment: 14 pages, 3 figures, published as technical report of the Department of Computer Science of RWTH Aachen Universit

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

Roles and responsibilities in agile ICT for development

This paper examines the different roles in designing interactive software in a ICT for development context. Using experiences from a participatory action research project, in which we used agile methods to design and deploy an system to support ‘agricultural information flow’ for a co-operative of small farmers in rural India, we identify points of difference between the roles in standard descriptions of agile software methods and the roles as they emerged in our project. A key finding is the critical role played by a ‘Development Project Manager’ in facilitating dialogue, orchestrating the activities of other actors and in building the capabilities and confidence of all the participants in joint action

International conference on software engineering and knowledge engineering: Session chair

The Thirtieth International Conference on Software Engineering and Knowledge Engineering (SEKE 2018) will be held at the Hotel Pullman, San Francisco Bay, USA, from July 1 to July 3, 2018. SEKE2018 will also be dedicated in memory of Professor Lofti Zadeh, a great scholar, pioneer and leader in fuzzy sets theory and soft computing. The conference aims at bringing together experts in software engineering and knowledge engineering to discuss on relevant results in either software engineering or knowledge engineering or both. Special emphasis will be put on the transference of methods between both domains. The theme this year is soft computing in software engineering & knowledge engineering. Submission of papers and demos are both welcome

Lean and green – a systematic review of the state of the art literature

The move towards greener operations and products has forced companies to seek alternatives to balance efficiency gains and environmental friendliness in their operations and products. The exploration of the sequential or simultaneous deployment of lean and green initiatives is the results of this balancing action. However, the lean-green topic is relatively new, and it lacks of a clear and structured research definition. Thus, this paper’s main contribution is the offering of a systematic review of the existing literature on lean and green, aimed at providing guidance on the topic, uncovering gaps and inconsistencies in the literature, and finding new paths for research. The paper identifies and structures, through a concept map, six main research streams that comprise both conceptual and empirical research conducted within the context of various organisational functions and industrial sectors. Important issues for future research are then suggested in the form of research questions. The paper’s aim is to also contribute by stimulating scholars to further study this area in depth, which will lead to a better understanding of the compatibility and impact on organisational performance of lean and green initiatives. It also holds important implications for industrialists, who can develop a deeper and richer knowledge on lean and green to help them formulate more effective strategies for their deployment

Addressing challenges to teach traditional and agile project management in academia

In order to prepare students for a professional IT career, most universities attempt to provide a current educational curriculum in the Project Management (PM) area to their students. This is usually based on the most promising methodologies used by the software industry. As instructors, we need to balance traditional methodologies focused on proven project planning and control processes leveraging widely accepted methods and tools along with the newer agile methodologies. Such new frameworks emphasize that software delivery should be done in a flexible and iterative manner and with significant collaboration with product owners and customers. In our experience agile methodologies have witnessed an exponential growth in many diverse software organizations, and the various agile PM tools and techniques will continue to see an increase in adoption in the software development sector. Reflecting on these changes, there is a critical need to accommodate best practices and current methodologies in our courses that deliver Project Management content. In this paper we analyse two of the most widely used methodologies for traditional and agile software development – the widely used ISO/PMBOK standard provided by the Project Management Institute and the well-accepted Scrum framework. We discuss how to overcome curriculum challenges and deliver a quality undergraduate PM course for a Computer Science and Information systems curricula. Based on our teaching experience in Europe and North America, we present a comprehensive comparison of the two approaches. Our research covers the main concepts, processes, and roles associated with the two PM frameworks and recommended learning outcomes. The paper should be of value to instructors who are keen to see their computing students graduate with a sound understanding of current PM methodologies and who can deliver real-world software products.Accepted manuscrip

FESTivE: an information system method to improve product designers and environmental experts information exchanges

Effective collaboration between product designers and environmental experts is an important driver for the ecodesign practice in industry. This paper investigates the principal functions required for such an e ective collaboration and aims at facilitating them. Product designers should be able to integrate the environmental parameters into their activities, and to exchange information dynamically with the environmental expert whenever needed during the design process. Therefore, the IT system should be in itself dynamic and exible to the integration of new concepts (knowledge, software). Recent developments in Model Driven Engineering (MDE) are showing some interesting results to gain exibility and dynamism in the IT system. Combining software interoperability using model federation based on MDE with the speci city of ecodesign practice in industry this paper proposes the FESTivE method for Federate EcodeSign Tool modEls. Experimented in two different industrial contexts the practical feasibility of FESTivE has been validated with practitioners. Results on the e ects of using FESTivE in industry shows that product designers and environmental experts are more equipped to anticipate and to respond to each other's needs at each stage of the design process of product or service

Software development methods and usability: Perspectives from a survey in the software industry in Norway

This paper investigates the relationship between traditional software development methodologies and usability. The point of departure is the assumption that two important disciplines in software development, one of software development methods (SDMs) and one of usability work, are not integrated in industrial software projects. Building on previous research we investigate two questions; (1) Will software companies generally acknowledge the importance of usability, but not prioritise it in industrial projects? and (2) To what degree are software development methods and usability perceived by practitioners as being integrated? To this end a survey in the Norwegian IT industry was conducted. From a sample of 259 companies we received responses from 78 companies. In response to our first research question, our findings show that although there is a positive bias towards usability, the importance of usability testing is perceived to be much less than that of usability requirements. Given the strong time and cost pressures associated with the software industry, we believe that these results highlight that there is a gap between intention and reality. Regarding our second research question our survey revealed that companies perceive usability and software development methods to be integrated. This is in contrast to earlier research, which, somewhat pessimistically, has argued for the existence of two different cultures, one of software development and one of usability. The findings give hope for the future, in particular because the general use of system development methods are pragmatic and adaptable