User experience (UX) is a quality aspect that considers the emotions evoked by the system, extending the usability concept beyond effectiveness, efficiency, and satisfaction. Practitioners and researchers are aware of the importance of evaluating UX. Thus, UX evaluation is a growing field with diverse approaches. Despite various approaches, most of them produce a general indication of the experience as a result and do not seek to capture the problem that gave rise to the bad UX. This information makes it difficult to obtain relevant results to improve the application, making it challenging to identify what caused a negative user experience. To address this gap, we developed a UX evaluation technique called UX-Tips. This paper presents UX-Tips and reports two empirical studies performed in an academic and an industrial setting to evaluate it. Our results show that UX-Tips had good performance in terms of efficiency and effectiveness, making it possible to identify the causes that led to a negative user experience, and it was easy to use. In this sense, we present a new technique suitable for use in both academic and industrial settings, allowing UX evaluation and finding the problems that may lead to a negative experience.
Software Quality is a relevant topic that interests both Academy and Industry. Hence, research on this topic should be aligned with the Industry needs, which demands the adoption of research approaches that enable closer interaction between researchers and practitioners. In this context, Design Science Research (DSR) stands out as a way to reduce the gap between theory and practice. DSR is a methodological approach to building innovative artifacts to solve real-world problems and, at the same time, making a scientific contribution. As a problem-oriented research method, DSR seeks to understand the problem, build and evaluate artifacts that allow transforming situations, changing their conditions to better or desirable states. In DSR projects, empirical studies have been usually applied to evaluate the proposed artifact. However, they can also be used to support other activities. Over the last eight years, we have successfully used empirical studies with different purposes in DSR projects. We organized the studies as learning iterations that provide useful knowledge to understand the problem, ground the artifact, develop, evaluate and improve it. As a result, we have experienced a more fluid DSR process and the proposed artifacts have been better grounded and suitable for solving the aimed problem. In this paper, we share our experience by discussing how we have used empirical studies as learning iterations in DSR projects, presenting our approach to organizing empirical studies in a DSR project according to the study purpose and the knowledge it intends to capture, and summarizing two DSR projects that address software quality issues and were developed by using such approach.
Information Systems (IS) industry has been pressured to deliver software products under reduced time-to-market and restrict budget. Agile Methodologies (AM) have been adopted to meet those aforementioned needs by the adoption of self-managing teams, iterative development cycles, fast delivery, and focus on functional software. Adoption of AM requires a suitable organizational environment, with significant changes in the employees’ behavior and in the working processes, impacting, and suffering the impact of Organizational Culture (OC). In this direction, methods, actions, and policies must be thought to align the company’s OC to the use of AM, in such a way that both can benefit each other. However, there is a lack of proposals that systematically investigate how to align both OC and AM. In this sense, a systematic mapping study (SMS) was conducted to identify studies that associate OC in initiatives of AM adoption. This paper presents the state-of-the-art about the influence of OC in the adoption of AM. The main contribution of this paper is bringing up an overview of the area, indicating perspectives of research, and exposing (i) a list of actions which have been reported to align OC and AM; (ii) OC factors recognized as essential to the successful adoption of AM; and (iii) the perceptions on a lack of awareness about the influence of OC in IT organizations.