English (United Kingdom)

https://curated-unify.zendy.io/wp-json/zendy-region/v1/featured_content/oa?rat=en

https://curated-unify.zendy.io/wp-json/zendy-region/v1/highlighted_journal/

Zendy Plus

Presents the access of premium content as premium feature

Premium Content

Presents the keyphrase highlighting as premium feature

Keyphrase Highlighting

Presents the summarisation as premium feature

Summarisation

Insights

Presents the pdf analysis as premium feature

PDF Analysis

Presents the zaia usage as premium feature

ZAIA

Zendy Tools

Zendy Open

Context: Contemporary software development is typically conducted in dynamic,resource-scarce environments that are prone to the accumulation of technicaldebt. While this general phenomenon is acknowledged, what remains unknown ishow technical debt specifically manifests in and affects software processes,and how the software development techniques employed accommodate or mitigatethe presence of this debt. Objectives: We sought to draw on practitionerinsights and experiences in order to classify the effects of agile method useon technical debt management. We explore the breadth of practitioners'knowledge about technical debt; how technical debt is manifested across thesoftware process; and the perceived effects of common agile softwaredevelopment practices and processes on technical debt. In doing so, we addressa research gap in technical debt knowledge and provide novel and actionablemanagerial recommendations. Method: We designed, tested and executed amulti-national survey questionnaire to address our objectives, receiving 184responses from practitioners in Brazil, Finland, and New Zealand. Results: Ourfindings indicate that: 1) Practitioners are aware of technical debt, although,there was under utilization of the concept, 2) Technical debt commonly residesin legacy systems, however, concrete instances of technical debt are hard toconceptualize which makes it problematic to manage, 3) Queried agile practicesand processes help to reduce technical debt; particularly, techniques thatverify and maintain the structure and clarity of implemented artifacts.Conclusions: The fact that technical debt instances tend to havecharacteristics in common means that a systematic approach to its management isfeasible. However, notwithstanding the positive effects of some agile practiceson technical debt management, competing stakeholders' interests remain aconcern.(Abridged)

Technical debt and agile software development practices and processes: An industry practitioner survey