Meta-ethnography to understand healthcare professionals’ experience of treating adults with chronic non-malignant pain

Objectives We aimed to explore healthcare professionals’ experience of treating chronic non-malignant pain by conducting a qualitative evidence synthesis. Understanding this experience from the perspective of healthcare professionals will contribute to improvements in the provision of care. Design Qualitative evidence synthesis using meta-ethnography. We searched five electronic bibliographic databases from inception to November 2016. We included studies that explore healthcare professionals’ experience of treating adults with chronic non-malignant pain. We used the GRADE-CERQual framework to rate confidence in review findings. Results We screened the 954 abstracts and 184 full texts and included 77 published studies reporting the experiences of over 1551 international healthcare professionals including doctors, nurses and other health professionals. We abstracted six themes: (1) a sceptical cultural lens, (2) navigating juxtaposed models of medicine, (3) navigating the geography between patient and clinician, (4) challenge of dual advocacy, (5) personal costs and (6) the craft of pain management. We rated confidence in review findings as moderate to high. Conclusions This is the first qualitative evidence synthesis of healthcare professionals’ experiences of treating people with chronic non-malignant pain. We have presented a model that we developed to help healthcare professionals to understand, think about and modify their experiences of treating patients with chronic pain. Our findings highlight scepticism about chronic pain that might explain why patients feel they are not believed. Findings also indicate a dualism in the biopsychosocial model and the complexity of navigating therapeutic relationships. Our model may be transferable to other patient groups or situations

Privacy Vulnerabilities in the Practices of Repairing Broken Digital Artifacts in Bangladesh

This paper presents a study on the privacy concerns associated with the practice of repairing broken digital objects in Bangladesh. Historically, repair of old or broken technologies has received less attention in ICTD scholarship than design, development, or use. As a result, the potential privacy risks associated with repair practices have remained mostly unaddressed. This paper describes our three-month long ethnographic study that took place at ten major repair sites in Dhaka, Bangladesh. We show a variety of ways in which the privacy of an individual’s personal data may be compromised during the repair process. We also examine people’s perceptions around privacy in repair, and its connections with their broader social and cultural values. Finally, we discuss the challenges and opportunities for future research to strengthen the repair ecosystem in developing countries. Taken together, our findings contribute to the growing discourse around post-use cycles of technology

Trading Discipline for Agility? Questioning the Unfaithful Appropriation of Agile Software Development Practices

Agile software development practices are rapidly replacing traditional and apparently more disciplined methodologies. However, empirical evidence suggests that organizations experience varying levels of success as more structured processes are traded for more agile ones. Using an autoethnographic approach, we reflect on how the various practices of XP discipline time-space relations amongst developer, customer and code. In this new form of disciplining, we contend that each actor is located in time and space in disciplined or controlled ways. We conclude that the faithful appropriation of the entire complement of agile development practices seems to be critical to the novel disciplinary positioning that they together collectively promote.

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

Using mobile RE tools to give end-users their own voice

Researchers highlight end-user involvement in system design as an important concept for developing useful and usable solutions. However, end-user involvement in software engineering is still an open-ended topic. Novel paradigms such as service-oriented computing strengthen the need for more active end-user involvement in order to provide systems that are tailored to individual end-user needs. Our work is based on the fact that the majority of end-users are familiar with mobile devices and use an increasing number of mobile applications. A mobile tool enabling end-user led requirements elicitation could be just one of many applications installed on end-users' mobile devices. In this paper, we present a framework of end-user involvement in requirements elicitation which motivates our research. The main contribution of our research is a tool-supported requirements elicitation approach allowing end-users to document needs in situ. Furthermore, we present first evaluation results to highlight the feasibility of on-site end-user led requirements elicitation

Collaboration and co-ordination in mature eXtreme programming teams

Mature eXtreme programming (XP) teams are highly collaborative and selforganising. In previous studies, we have observed that these teams rely on two apparently simple mechanisms of co-ordination and collaboration: story cards and the Wall. Story cards capture and embody the user stories which form the basis of implementation, while the Wall is a physical space used to organise and display the cards being implemented during the current development cycle (called an iteration). In this paper we analyse the structure and use of story cards and the Wall in three mature XP teams, using a distributed cognition approach. The teams work in different commercial organisations developing different systems, yet we find significant similarities between their use of these two artefacts. Although simple, teams use the cards and the Wall in sophisticated ways to represent and communicate information that is vital to support their activities. We discuss the significance of the physical medium for the story cards and the Wall in an XP team and discuss the considerations that need to be taken into account for the design of technology to support the teams

Preventing Incomplete/Hidden Requirements: Reflections on Survey Data from Austria and Brazil

Many software projects fail due to problems in requirements engineering (RE). The goal of this paper is analyzing a specific and relevant RE problem in detail: incomplete/hidden requirements. We replicated a global family of RE surveys with representatives of software organizations in Austria and Brazil. We used the data to (a) characterize the criticality of the selected RE problem, and to (b) analyze the reported main causes and mitigation actions. Based on the analysis, we discuss how to prevent the problem. The survey includes 14 different organizations in Austria and 74 in Brazil, including small, medium and large sized companies, conducting both, plan-driven and agile development processes. Respondents from both countries cited the incomplete/hidden requirements problem as one of the most critical RE problems. We identified and graphically represented the main causes and documented solution options to address these causes. Further, we compiled a list of reported mitigation actions. From a practical point of view, this paper provides further insights into common causes of incomplete/hidden requirements and on how to prevent this problem.Comment: in Proceedings of the Software Quality Days, 201