000 03655naa a22005057i 4500
001 UMUN-OA-20261005-SE-013
003 local
005 20261005174819.0
006 m o d
007 cr||||||||||||
008 261005s2024 xx o u000 0 eng d
024 7 _a10.1016/j.jss.2024.111966
_2doi
035 _a(local)OpenAlex:W4391247856
040 _alocal
_beng
_clocal
041 0 _aeng
100 0 _aJan-Niklas Meckenstock
_eauthor.
245 1 0 _aShedding light on the dark side – A systematic literature review of the issues in agile software development methodology use /
_cJan-Niklas Meckenstock.
264 1 _a[Place of publication not identified] :
_bElsevier BV,
_c2024.
300 _a1 online resource (1 article).
336 _atext
_btxt
_2rdacontent
337 _acomputer
_bc
_2rdamedia
338 _aonline resource
_bcr
_2rdacarrier
500 _aPublication type: Review article.
500 _aLinked open-access copy: published version.
506 0 _aOpen access; no subscription required for the linked open-access version.
_fUnrestricted online access
_2star
520 3 _aAgile software development (ASD) methodologies address problems of traditional approaches, but can also cause various issues. A systematization of the spectrum of negative facets and how they arise has not been developed, leaving the dark side of ASD opaque. The paper systematizes findings on various negative facets to define what specific issues constitute the dark side of ASD. It also examines how relationships among these issues define the complexity of the downside. A literature review of 70 articles was conducted following Kitchenham & Charters (2007). The content analysis employed the coding procedure by Gioia et al. (2013) to systematize the negative aspects of ASD methodologies. The paper reveals 90 issues, grouped into 18 coherent themes. Six levels of manifestation point to the primarily affected constituents in ASD projects. In addition, 65 relationships among issues are explored, providing explanations for the complexity of the dark side of ASD. The systematization shows what aspects constitute the dark side of ASD, emphasizing its multidimensional nature along issues such as reduced developer well-being, product quality and development productivity. The analysis of how its complexity is defined reveals that customer misbehavior and delivery pressure are significant origins of other issues.
540 _aCreative Commons Attribution (licence family recorded by the source; version not supplied in metadata).
_uhttps://openalex.org/W4391247856
546 _aIn English.
588 0 _aDescription generated from OpenAlex bibliographic metadata retrieved on 5 October 2026; full text linked from the source.
590 _aCourse allocation: B. Sc. Software Engineering.
650 4 _aagile software development
650 4 _adeveloper well-being
650 4 _aproduct quality
650 4 _adevelopment productivity
650 4 _acustomer misbehavior
650 4 _adelivery pressure
653 _aB. Sc. Software Engineering
653 _aUMUN open access collection
653 _aagile software
655 4 _aReview articles.
773 0 _tJournal of Systems and Software
_gVol. 211, (2024), pages/article 111966
_x0164-1212
856 4 0 _uhttps://doi.org/10.1016/j.jss.2024.111966
_yRead open-access publication
_zOpen access. Access and licence reported by the source; this host could not be independently checked by automation.
_70
884 _aCourse selection and automated MARC21 enrichment from OpenAlex metadata.
_g20261005
_khttps://openalex.org/W4391247856
_qlocal
942 _n0
999 _c505
_d505