Architecture and Technical Debt Agile Planning Methodology for Software Production

Elgebeely, Aya; Kamel, Amr

doi:10.5121/csit.2017.71703

Cited by 1 publication

(1 citation statement)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…-agile teams have a known prowess in developing software [8,9], but nobody has addressed yet whether the organisational structures behind agile teams exhibit known community smells [5] which could be potentially corrected for further organisational improvement; (2) to what extent do community smells in agile organisational structures reflect good software quality outputs? -as a proxy to software quality we consider software architecture smells [10,11] that is, known patterns that may cause nasty software maintenance and evolution issues [11] and which may cause technical debt [12,13].…”

Section: Introductionmentioning

confidence: 99%

Splicing Community and Software Architecture Smells in Agile Teams: An industrial Study

Tamburri¹,

Kazman²,

Heuvel³

2019

Proceedings of the Annual Hawaii International Conference on System Sciences

View full text Add to dashboard Cite

Software engineering nowadays largely relies on agile methods to carry out software development. In often highly distributed organizations, agile teams can develop organisational and socio-technical issues loosely defined as community smells, which reflect sub-optimal organisational configurations that bear additional project cost, a phenomenon called social debt. In this paper we look into the co-occurrence of such nasty organisational phenomena-community smells-with software architecture smells-indicators that software architectures may exhibit sub-optimal modularization structures, with consequent additional cost. We conclude that community smells can serve as a guide to steer the qualities of software architectures within agile teams.

show abstract