Sökning: (WFRF:(Svensson Richard)) srt2:(2015-2019) >
An exploratory stud...
An exploratory study of waste in software development organizations using agile or lean approaches : A multiple case study at 14 organizations
-
- Alahyari, Hiva, 1979 (författare)
- Gothenburg University,Göteborgs universitet,Institutionen för data- och informationsteknik (GU),Department of Computer Science and Engineering (GU),Chalmers, SWE
-
- Gorschek, Tony, 1972- (författare)
- Blekinge Tekniska Högskola,Institutionen för programvaruteknik,Blekinge Tekniska Högskola, BTH
-
- Berntsson Svensson, Richard, 1978- (författare)
- Blekinge Tekniska Högskola,Institutionen för programvaruteknik,Blekinge Tekniska Högskola, BTH
-
(creator_code:org_t)
- Elsevier B.V. 2019
- 2019
- Engelska.
-
Ingår i: Information and Software Technology. - : Elsevier B.V.. - 0950-5849 .- 1873-6025. ; 107, s. 78-94
- Relaterad länk:
-
https://urn.kb.se/re...
-
visa fler...
-
https://doi.org/10.1...
-
https://research.cha...
-
https://gup.ub.gu.se...
-
visa färre...
Abstract
Ämnesord
Stäng
- Context: The principal focus of lean is the identification and elimination of waste from the process with respect to maximizing customer value. Similarly, the purpose of agile is to maximize customer value and minimize unnecessary work and time delays. In both cases the concept of waste is important. Through an empirical study, we explore how waste is approached in agile software development organizations. Objective: This paper explores the concept of waste in agile/lean software development organizations and how it is defined, used, prioritized, reduced, or eliminated in practice Method: The data were collected using semi-structured open-interviews. 23 practitioners from 14 embedded software development organizations were interviewed representing two core roles in each organization. Results: Various wastes, categorized in 10 different categories, were identified by the respondents. From the mentioned wastes, not all were necessarily waste per se but could be symptoms caused by wastes. From the seven wastes of lean, Task-switching was ranked as the most important, and Extra-features, as the least important wastes according to the respondents’ opinion. However, most companies do not have their own or use an established definition of waste, more importantly, very few actively identify or try to eliminate waste in their organizations beyond local initiatives on project level. Conclusion: In order to identify, recognize and eliminate waste, a common understanding, and a joint and holistic view of the concept is needed. It is also important to optimize the whole organization and the whole product, as waste on one level can be important on another, thus sub-optimization should be avoided. Furthermore, to achieve a sustainable and effective waste handling, both the short-term and the long-term perspectives need to be considered. © 2018 Elsevier B.V.
Ämnesord
- NATURVETENSKAP -- Data- och informationsvetenskap -- Programvaruteknik (hsv//swe)
- NATURAL SCIENCES -- Computer and Information Sciences -- Software Engineering (hsv//eng)
- TEKNIK OCH TEKNOLOGIER -- Naturresursteknik -- Miljöledning (hsv//swe)
- ENGINEERING AND TECHNOLOGY -- Environmental Engineering -- Environmental Management (hsv//eng)
- TEKNIK OCH TEKNOLOGIER -- Maskinteknik -- Tillförlitlighets- och kvalitetsteknik (hsv//swe)
- ENGINEERING AND TECHNOLOGY -- Mechanical Engineering -- Reliability and Maintenance (hsv//eng)
Nyckelord
- Agile software development
- Lean software development
- Non-value adding activities
- Waste
- Wastes
- Empirical studies
- Exploratory studies
- Long-term perspective
- Multiple-case study
- Software development organizations
- Value adding activities
- Software design
- Waste
- Non-value adding activities
- Lean software development
- Agile software development
- management
Publikations- och innehållstyp
- ref (ämneskategori)
- art (ämneskategori)
Hitta via bibliotek
Till lärosätets databas