Subscribe to the gold package and get unlimited access to Shamra Academy
Register a new userLibrary Adoption Dynamics in Software Teams
54
0
0.0
(
0
)
Added by
Tim Weninger PhD
Publication date
2020
fields
Informatics Engineering
and research's language is
English
Ask ChatGPT about the research
No Arabic abstract
When a group of people strives to understand new information, struggle ensues as various ideas compete for attention. Steep learning curves are surmounted as teams learn together. To understand how these team dynamics play out in software development, we explore Git logs, which provide a complete change history of software repositories. In these repositories, we observe code additions, which represent successfully implemented ideas, and code deletions, which represent ideas that have failed or been superseded. By examining the patterns between these commit types, we can begin to understand how teams adopt new information. We specifically study what happens after a software library is adopted by a project, i.e. when a library is used for the first time in the project. We find that a variety of factors, including team size, library popularity, and prevalence on Stack Overflow are associated with how quickly teams learn and successfully adopt new software libraries.
rate research
Read More
Diffusion channels are critical to determining the adoption scale which leads to the ultimate impact of an innovation. The aim of this study is to develop an integrative understanding of the impact of two diffusion channels (i.e., broadcasting vs virality) on innovation adoption. Using citations of a series of classic algorithms and the time series of co-authorship as the footprints of their diffusion trajectories, we propose a novel method to analyze the intertwining relationships between broadcasting and virality in the innovation diffusion process. Our findings show that broadcasting and virality have similar diffusion power, but play different roles across diffusion stages. Broadcasting is more powerful in the early stages but may be gradually caught up or even surpassed by virality in the later period. Meanwhile, diffusion speed in virality is significantly faster than broadcasting and members from virality channels tend to adopt the same innovation repetitively.
When a group of people strives to understand new information, struggle ensues as various ideas compete for attention. Steep learning curves are surmounted as teams learn together. To understand how these team dynamics play out in software development, we explore Git logs, which provide a complete change history of software repositories. In these repositories, we observe code additions, which represent successfully implemented ideas, and code deletions, which represent ideas that have failed or been superseded. By examining the patterns between these commit types, we can begin to understand how teams adopt new information. We specifically study what happens after a software library is adopted by a project, i.e., when a library is used for the first time in the project. We find that a variety of factors, including team size, library popularity, and prevalence on Stack Overflow are associated with how quickly teams learn and successfully adopt new software libraries.
Purpose: The purpose of this paper is to explore possible factors impacting team performance in healthcare, by focusing on information exchange within and across hospitals boundaries. Design/methodology/approach: Through a web-survey and group interviews, the authors collected data on the communication networks of 31 members of four interdisciplinary healthcare teams involved in a system redesign initiative within a large US childrens hospital. The authors mapped their internal and external social networks based on management advice, technical support and knowledge dissemination within and across departments, studying interaction patterns that involved more than 700 actors. The authors then compared team performance and social network metrics such as degree, closeness and betweenness centrality, and computed cross ties and constraint levels for each team. Findings: The results indicate that highly effective teams were more inwardly focused and less connected to outside members. Moreover, highly recognized teams communicated frequently but, overall, less intensely than the others. Originality/value: Mapping knowledge flows and balancing internal focus and outward connectivity of interdisciplinary teams may help healthcare decision makers in their attempt to achieve high value for patients, families and employees.
Agile methods are best taught in a hands-on fashion in realistic projects. The main challenge in doing so is to assess whether students apply the methods correctly without requiring complete supervision throughout the entire project. This paper presents experiences from a classroom project where 38 students developed a single system using a scaled version of Scrum. Surveys helped us to identify which elements of Scrum correlated most with student satisfaction or posed the biggest challenges. These insights were augmented by a team of tutors, which accompanied main meetings throughout the project to provide feedback to the teams, and captured impressions of method application in practice. Finally, we performed a post-hoc, tool-supported analysis of collaboration artifacts to detect concrete indicators for anti-patterns in Scrum adoption. Through the combination of these techniques we were able to understand how students implemented Scrum in this course and which elements require further lecturing and tutoring in future iterations. Automated analysis of collaboration artifacts proved to be a promising addition to the development process that could potentially reduce manual efforts in future courses and allow for more concrete and targeted feedback, as well as more objective assessment.
The Long Wavelength Array Software Library (LSL) is a Python module that provides a collection of utilities to analyze and export data collected at the first station of the Long Wavelength Array, LWA1. Due to the nature of the data format and large-N ($gtrsim$100 inputs) challenges faced by the LWA, currently available software packages are not suited to process the data. Using tools provided by LSL, observers can read in the raw LWA1 data, synthesize a filter bank, and apply incoherent de-dispersion to the data. The extensible nature of LSL also makes it an ideal tool for building data analysis pipelines and applying the methods to other low frequency arrays.
Log in to be able to interact and post comments
comments
Fetching comments
Sign in to be able to follow your search criteria
