No abstract

No abstract

No abstract

No abstract

While onboarding an open source software (OSS) project, contributors face many different barriers that hinder their contribution, leading in many cases to dropouts. Many projects leverage the contribution of outsiders and the sustainability of the project relies on retaining some of these newcomers. In this paper, we discuss some barriers faced by newcomers to OSS. The barriers were identified using a qualitative analysis on data obtained from newcomers and members of OSS projects. We organize the results in a conceptual model composed of 38 barriers, grouped into seven different categories. These barriers may motivate new studies and the development of appropriate tooling to better support the onboarding of new developers.

Together with many success stories, promises such as the increase in production speed and the improvement in stakeholders' collaboration have contributed to making agile a transformation in the software industry in which many companies want to take part. However, driven either by a natural and expected evolution or by contextual factors that challenge the adoption of agile methods as prescribed by their creator(s), software processes in practice mutate into hybrids over time. Are these still agile? In this article, we investigate the question: what makes a software development method agile? We present an empirical study grounded in a large-scale international survey that aims to identify software development methods and practices that improve or tame agility. Based on 556 data points, we analyze the perceived degree of agility in the implementation of standard project disciplines and its relation to used development methods and practices. Our findings suggest that only a small number of participants operate their projects in a purely traditional or agile manner (under 15%). That said, most project disciplines and most practices show a clear trend towards increasing degrees of agility. Compared to the methods used to develop software, the selection of practices has a stronger effect on the degree of agility of a given discipline. Finally, there are no methods or practices that explicitly guarantee or prevent agility. We conclude that agility cannot be defined solely at the process level. Additional factors need to be taken into account when trying to implement or improve agility in a software company. Finally, we discuss the field of software process-related research in the light of our findings and present a roadmap for future research.

Resumo. Este artigo apresenta uma técnica de inspeção de usabilidade (WDP -Web Design Perspectives-Based Usability Evaluation) e a metodologia experimental utilizada como base para seu desenvolvimento e aprimoramento. Até o presente momento foram executados três estudos experimentais (um secundário e dois primários) que levaram à versão atual da técnica WDP. Resultados indicam que a técnica é viável e que é possivelmente mais efetiva e tão eficiente quanto a Avaliação Heurística proposta por Nielsen. Abstract. This work describes a usability inspection technique (WDP -WebDesign Perspectives-Based Usability Evaluation) as well as the experimentation methodology followed to support its development and improvement. At this point in time, three experimental studies (one secondary and two primaries) were carried out and led to the WDP's current version. Results indicate the feasibility of the WDP technique and its possibility to be more effective than and as efficient as Nielsen's Heuristics Evaluation.

No abstract