Does Socio-Technical Congruence Have an Effect on Software Build Success? A Study of Coordination in a Software Project

Kwan, Irwin; Schröter, Adrian; Damian, Daniela

doi:10.1109/tse.2011.29

Cited by 112 publications

(67 citation statements)

References 45 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Similar works (e.g. [18]), can be used as starting points to evaluate metrics for social debt. Perhaps socio-technical congruence represents a first rudimental metric for social debt in certain development communities.…”

Section: State Of the Artmentioning

confidence: 99%

Social debt in software engineering: insights from industry

Tamburri¹,

Kruchten

Lago³

et al. 2015

J Internet Serv Appl

170

View full text Add to dashboard Cite

Social debt is analogous to technical debt in many ways: it represents the state of software development organisations as the result of "accumulated" decisions. In the case of social debt, decisions are about people and their interactions. Our objective was to study the causality around social debt in practice. In so doing, we conducted exploratory qualitative research in a large software company. We found many forces together causing social debt; we represented them in a framework, and captured anti-patterns that led to the debt in the first place. Finally, we elicited best practices that technicians adopted to pay back some of the accumulated debt. We learned that social debt is strongly correlated with technical debt and both forces should be reckoned with together during the software process.

show abstract

Section: State Of the Artmentioning

confidence: 99%

Social debt in software engineering: insights from industry

Tamburri¹,

Kruchten

Lago³

et al. 2015

J Internet Serv Appl

170

View full text Add to dashboard Cite

show abstract

“…For example, Cataldo et al introduced the notion of socio-technical congruence, and provided evidence that developers who share information when making changes in dependent software components complete tasks in less time [15]. Other researchers similarly showed that missing information correlates with coordination problems and project failures [14,63,47]. Ko et al analyzed the information needs of developers in collocated teams and found they have difficulties in answering questions related to information about colleagues' work and software component dependencies [45].…”

Section: Discussionmentioning

confidence: 99%

Supporting Developers' Coordination in the IDE

Guzzi

Bacchelli

Riche

et al. 2015

Proceedings of the 18th ACM Conference on Computer Supported Cooperative Work &Amp; Social Computing

View full text Add to dashboard Cite

Teamwork in software engineering is time-consuming and problematic. In this paper, we explore how to better support developers' collaboration in teamwork, focusing on the software implementation phase happening in the integrated development environment (IDE). Conducting a qualitative investigation, we learn that developers' teamwork needs mostly regard coordination, rather than concurrent work on the same (sub)task, and that developers successfully deal with scenarios considered problematic in literature, but they have problems dealing with breaking changes made by peers on the same project. We derive implications and recommendations. Based on one of the latter, we analyze the current IDE support for receiving code changes, finding that historical information is neither visible nor easily accessible. Consequently, we devise and qualitatively evaluate BELLEVUE, the design of an IDE extension to make received changes always visible and code history accessible in the editor.

show abstract

“…Upon inspection of the actual coordination activities a match between coordination requirements and activities may be established; such a match has proven to be beneficial to several aspects of software development, for instance reducing the resolution time of modification requests [15] or software build success [16].…”

Section: Theoretical Backgroundmentioning

confidence: 99%

Competencies outside Agile Teams’ Borders: The Extended Scrum Team

Wagenaar¹,

Overbeek²,

Helms³

2016

Annals of Computer Science and Information Systems

View full text Add to dashboard Cite

Abstract-According to the Scrum process framework a Scrum team should have all necessary competencies to accomplish its work. Fragmented and anecdotal evidence hints at Scrum teams still needing additional, external competencies. To contribute to theories on Scrum team composition and practitioner's concerns in staffing a Scrum team we investigated Scrum teams' cross-functionality: To whom do Scrum teams turn for additional competencies, which competencies are involved and how are Scrum teams aware of additional competencies they need? To this extent we analysed the communication in three Scrum teams during one of their Sprints. Our results show that additional competencies are called for, not only on an ad hoc basis, but also on a structural basis. To include those structural competencies the notion of an extended Scrum team is introduced.

show abstract

Does Socio-Technical Congruence Have an Effect on Software Build Success? A Study of Coordination in a Software Project

Cited by 112 publications

References 45 publications

Social debt in software engineering: insights from industry

Social debt in software engineering: insights from industry

Supporting Developers' Coordination in the IDE

Competencies outside Agile Teams’ Borders: The Extended Scrum Team

Contact Info

Product

Resources

About