11,533 research outputs found

    Bridging the gap between research and agile practice: an evolutionary model

    Get PDF
    There is wide acceptance in the software engineering field that industry and research can gain significantly from each other and there have been several initiatives to encourage collaboration between the two. However there are some often-quoted challenges in this kind of collaboration. For example, that the timescales of research and practice are incompatible, that research is not seen as relevant for practice, and that research demands a different kind of rigour than practice supports. These are complex challenges that are not always easy to overcome. Since the beginning of 2013 we have been using an approach designed to address some of these challenges and to bridge the gap between research and practice, specifically in the agile software development arena. So far we have collaborated successfully with three partners and have investigated three practitioner-driven challenges with agile. The model of collaboration that we adopted has evolved with the lessons learned in the first two collaborations and been modified for the third. In this paper we introduce the collaboration model, discuss how it addresses the collaboration challenges between research and practice and how it has evolved, and describe the lessons learned from our experience

    Protocol and tools for conducting agile software engineering research in an industrial-academic setting: a preliminary study

    Get PDF
    Conducting empirical research in software engineering industry is a process, and as such, it should be generalizable. The aim of this paper is to discuss how academic researchers may address some of the challenges they encounter during conducting empirical research in the software industry by means of a systematic and structured approach. The protocol developed in this paper should serve as a practical guide for researchers and help them with conducting empirical research in this complex environment.Peer ReviewedPostprint (author's final draft

    Protocol and Tools for Conducting Agile Software Engineering Research in an Industrial-Academic Setting: A Preliminary Study

    Full text link
    Conducting empirical research in software engineering industry is a process, and as such, it should be generalizable. The aim of this paper is to discuss how academic researchers may address some of the challenges they encounter during conducting empirical research in the software industry by means of a systematic and structured approach. The protocol developed in this paper should serve as a practical guide for researchers and help them with conducting empirical research in this complex environment.Comment: Accepted to CESI 2018 - International Workshop on Conducting Empirical Studies in Industry (in conjunction with ICSE 2018

    Industry–Academia Research Collaboration and Knowledge Co-creation: Patterns and Anti-patterns

    Get PDF
    Increasing the impact of software engineering research in the software industry and the society at large has long been a concern of high priority for the software engineering community. The problem of two cultures, research conducted in a vacuum (disconnected from the real world), or misaligned time horizons are just some of the many complex challenges standing in the way of successful industry–academia collaborations. This article reports on the experience of research collaboration and knowledge co-creation between industry and academia in software engineering as a way to bridge the research–practice collaboration gap. Our experience spans 14 years of collaboration between researchers in software engineering and the European and Norwegian software and IT industry. Using the participant observation and interview methods, we have collected and afterwards analyzed an extensive record of qualitative data. Drawing upon the findings made and the experience gained, we provide a set of 14 patterns and 14 anti-patterns for industry–academia collaborations, aimed to support other researchers and practitioners in establishing and running research collaboration projects in software engineering.publishedVersio

    MIXED METHOD COLLABORATION IN THE BUILT ENVIRONMENT

    Get PDF
    The built environment discipline or inter-discipline is a relatively new field in academic research. Its subject matter however is based on the traditional disciplines of the construction and property industries. Determining your ontological position and epistemological approach based on the researchparadigm of one of these fields’ may not provide an adequate solution to your research objectives.This paper outlines that framing your research within the broader confines of the built environment; drawing from related fields in an integrated manner may provide a more successful outcome.Arguments whether the built environment is an academic discipline or even the range of subjects thatmake up the discipline, although worthwhile, do not provide any meaningful insight into the issues andneeds of society that are served by the practice orientated fields that constitute the inter-discipline. A more valuable argument is whether built environment knowledge produced in academic circles is transferable to the practitioners providing services within its borders and ultimately how this knowledge contributes to the real issues and needs of society. This paper outlines a number of eminent authors that state a disconnect exists between academic research and fulfilling the needs of construction and property industries. The alleged gap between research and practice maybe a result of the prevalent positivist paradigm which exists in academia or/and the positivist application of tools in a practical context. In the built environment many innovative solutions are based on knowledge and experience acquired over many years of practice based application. Externalising this tacit knowledge should be the goal of academics and practitioners, thus filling in the gaps and making explicit what were originally hidden. This paper outlines that knowledge in the built environment would be etter served by an approach that combines the strengths of both a positivist and interpretist approach, giving rise to a plural research perspective

    Energizing collaborative industry‑academia learning: a present case and future visions

    Get PDF
    In Industry-Academia Collaborations (IAC) both academic, scientific research results and industrial practitioner findings and experiences are produced. Both types of knowledge should be gathered, codified, and disseminated efficiently and effectively. This paper investigates a recent (2014-2017) large-scale IAC R&D&I program case (Need for Speed, N4S) from a learning perspective. It was one of the programs in the Finnish SHOK (Strategic Centres of Science, Technology, and Innovation) system. The theoretical bases are in innovation management, knowledge management, and higher education (university) pedagogy. In the future, IAC projects should be more and more commonplace since major innovations are hardly ever done in isolation, not even by the largest companies. Both intra-organizational and inter-organizational learning networks are increasingly critical success factors. Collaborative learning capabilities will thus be required more often from all the participating parties. Efficient and effective knowledge creation and sharing are underpinning future core competencies. In this paper, we present and evaluate a collaboratively created and publicly shared digital knowledge repository called "Treasure Chest" produced during our case program. The starting point was a jointly created Strategic Research and Innovation Agenda (SRIA), which defined the main research themes and listed motivating research questions to begin with-i.e., intended learning outcomes (ILO). During the 4-year program, our collaborative industry-academia (I-A) learning process produced a range of theoretical and empirical results, which were iteratively collected and packaged into the Treasure Chest repository. Outstandingly, it contained, in addition to traditional research documents, narratives of the industrial learning experiences and more than 100 actionable knowledge items. In conclusion, our vision of the future is that such transparently shared, ambitious, and versatile outcome goals with a continuous integrative collection of the results are keys to effective networked I-A collaboration and learning. In that way, the N4S largely avoided the general problem of often conflicting motives between industrial firms seeking answers and applied solutions to their immediate practical problems and academic researchers aiming at more generalizable knowledge creation and high-quality scientific publications.Peer reviewe

    Industry-academia collaborations in software testing: experience and success stories from Canada and Turkey : Special Issue Industry Academia Collaborations in Software Testing

    Get PDF
    Collaboration between industry and academia supports improvement and innovation in industry and helps to ensure industrial relevance in academic research. However, many researchers and practitioners believe that the level of joint industry–academia collaborations (IAC) in software engineering (SE) is still relatively very low, compared to the amount of activity in each of the two communities. The goal of the empirical study reported in this paper is to characterize a set of collaborative industry–academia R&D projects in the area of software testing conducted by the authors (based in Canada and Turkey) with respect to a set of challenges, patterns and anti-patterns identified by a recent Systematic Literature Review study, with the aim of contributing to the body of evidence in the area of IAC, for the benefit of SE researchers and practitioners in conducting successful IAC projects in software testing and in software engineering in general. To address the above goal, a pool of ten IAC projects (six completed, two failed and two ongoing) all in the area of software testing, which the authors have led or have had active roles in, were selected as objects of study and were analyzed (both quantitatively and qualitatively) with respect to the set of selected challenges, patterns and anti-patterns. As outputs, the study presents a set of empirical findings and evidence-based recommendations, e.g.: it has been observed that even if an IAC project may seem perfect from many aspects, one single major challenge (e.g., disagreement in confidentiality agreements) can lead to its failure. Thus, we recommend that both parties (academics and practitioners) consider all the challenges early on and proactively work together to eliminate the risk of challenges in IAC projects. We furthermore report correlation and interrelationship of challenges, patterns and anti-patterns with project success measures. This study hopes to encourage and benefit other SE researchers and practitioners in conducting successful IAC projects in software testing and in software engineering in general in the future

    Exploring ML testing in practice - Lessons learned from an interactive rapid review with Axis Communications

    Get PDF
    There is a growing interest in industry and academia in machine learning (ML) testing. We believe that industry and academia need to learn together to produce rigorous and relevant knowledge. In this study, we initiate a collaboration between stakeholders from one case company, one research institute, and one university. To establish a common view of the problem domain, we applied an interactive rapid review of the state of the art. Four researchers from Lund University and RISE Research Institutes and four practitioners from Axis Communications reviewed a set of 180 primary studies on ML testing. We developed a taxonomy for the communication around ML testing challenges and results and identified a list of 12 review questions relevant for Axis Communications. The three most important questions (data testing, metrics for assessment, and test generation) were mapped to the literature, and an in-depth analysis of the 35 primary studies matching the most important question (data testing) was made. A final set of the five best matches were analysed and we reflect on the criteria for applicability and relevance for the industry. The taxonomies are helpful for communication but not final. Furthermore, there was no perfect match to the case company’s investigated review question (data testing). However, we extracted relevant approaches from the five studies on a conceptual level to support later context-specific improvements. We found the interactive rapid review approach useful for triggering and aligning communication between the different stakeholders

    Building Stronger Bridges: Strategies for Improving Communication and Collaboration Between Industry and Academia in Software Engineering

    Get PDF
    Background: The software engineering community has expressed growing concern regarding the need for more connections between research and practice. Despite the large amount of knowledge researchers generate, its impact on real-world practice is uncertain. Meanwhile, practitioners in industry often struggle to access and utilize relevant research outcomes that could inform and enhance their work. Collaboration between industry and academia is seen as a potential solution to bridge this gap, ensuring that research remains relevant and applicable in real-world contexts.Objective: This research aims to explore challenges in communication and collaboration between industry and to design, evaluate, and implement strategies that foster this collaboration. Methodology: The design science paradigm inspires this research, as we aim to obtain knowledge about industry-academia communication and collaboration by studying challenges and solutions in context. The thesis includes case studies; some are exploratory, while others focus on evaluating specific strategies.Results: In terms of problem understanding, we identified challenges that impact communication and collaboration, such as different expectations, perspectives, and ways of working. Furthermore, we pinpointed factors facilitating communication, including long-term projects, research relevance, and practitioners' involvement.Regarding how to improve communication and collaboration, we investigated two strategies. The first strategy involves using the SERP-taxonomy approach in a project on software vulnerability management in IoT systems. The second strategy involves the proposal of interactive rapid reviews, conducted in close collaboration with practitioners. We share the lessons from conducting two reviews (one in testing machine learning systems and the other in software component selection). The benefits of conducting interactive rapid reviews include mutual understanding, the development of networks, and increased motivation for further studies.Conclusion: The thesis emphasizes the importance of industry-academia collaboration as a key aspect in closing gaps between research and practice. The strategies discussed provide tools to understand industry-academia partnerships better and support future collaborations

    Involving External Stakeholders in Project Courses

    Full text link
    Problem: The involvement of external stakeholders in capstone projects and project courses is desirable due to its potential positive effects on the students. Capstone projects particularly profit from the inclusion of an industrial partner to make the project relevant and help students acquire professional skills. In addition, an increasing push towards education that is aligned with industry and incorporates industrial partners can be observed. However, the involvement of external stakeholders in teaching moments can create friction and could, in the worst case, lead to frustration of all involved parties. Contribution: We developed a model that allows analysing the involvement of external stakeholders in university courses both in a retrospective fashion, to gain insights from past course instances, and in a constructive fashion, to plan the involvement of external stakeholders. Key Concepts: The conceptual model and the accompanying guideline guide the teachers in their analysis of stakeholder involvement. The model is comprised of several activities (define, execute, and evaluate the collaboration). The guideline provides questions that the teachers should answer for each of these activities. In the constructive use, the model allows teachers to define an action plan based on an analysis of potential stakeholders and the pedagogical objectives. In the retrospective use, the model allows teachers to identify issues that appeared during the project and their underlying causes. Drawing from ideas of the reflective practitioner, the model contains an emphasis on reflection and interpretation of the observations made by the teacher and other groups involved in the courses. Key Lessons: Applying the model retrospectively to a total of eight courses shows that it is possible to reveal hitherto implicit risks and assumptions and to gain a better insight into the interaction...Comment: Abstract shortened since arxiv.org limits length of abstracts. See paper/pdf for full abstract. Paper is forthcoming, accepted August 2017. Arxiv version 2 corrects misspelled author nam
    • …
    corecore