Exploring the Sources of Waste in Kanban Software Development Projects

Ikonen, Marko; Kettunen, Petri; Oza, Nilay; Abrahamsson, Pekka

doi:10.1109/seaa.2010.40

Cited by 32 publications

(26 citation statements)

References 6 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Existing software development literature generally considers task switching to be a wasteful practice that should be prevented whenever possible [8][9][10].…”

Section: Software Development: Interruptions and Multiple Projectsmentioning

confidence: 99%

“…Finishing them sequentially maximises revenue, because most often the revenue diminishes over time [11]. Another argument is that switching between tasks (e.g., across projects) is considered as waste [9]. Concrete numbers on the waste are hard to find; practitioners claim a small production increase from going from one to two projects (70 % to 80 % effectiveness) and a steady decline in effective hours when adding more projects: 60 % with three, 45 % with four and 35 % with five simultaneous projects [8].…”

Section: Software Development: Interruptions and Multiple Projectsmentioning

confidence: 99%

See 1 more Smart Citation

Team Portfolio Scrum: An Action Research on Multitasking in Multi-project Scrum Teams

Stettina

Smit

2016

Agile Processes, in Software Engineering, and Extreme Programming

View full text Add to dashboard Cite

Abstract. Multi-project agile software development is a relatively new area of research. While original Scrum caters to co-located teams working on a single project, multi-project Scrum teams are a day-to-day reality, especially in small organizations. Multitasking across projects is frequently associated with loss of effectiveness, but this assumption is not sufficiently supported by empirical evidence. In order to better understand the phenomenon, we review existing literature across scientific domains and execute an action research project. Our findings show that the Team Portfolio Scrum (TPS) practice designed to support multitasking across projects is perceived to be useful, but with an associated increase in overhead.

show abstract

“…Existing software development literature generally considers task switching to be a wasteful practice that should be prevented whenever possible [8][9][10].…”

Section: Software Development: Interruptions and Multiple Projectsmentioning

confidence: 99%

Section: Software Development: Interruptions and Multiple Projectsmentioning

confidence: 99%

Team Portfolio Scrum: An Action Research on Multitasking in Multi-project Scrum Teams

Stettina

Smit

2016

Agile Processes, in Software Engineering, and Extreme Programming

View full text Add to dashboard Cite

show abstract

“…Software development operates in a repetitive environment [8,2]. In general, the productivity of KANBAN is remarkable [7,1], [9,11], [6,169]! To enhance the productivity, requirements specifications have to be qualitative [11,1].…”

Section: Theorymentioning

confidence: 99%

“…Lean approaches like KANBAN require a reliable quality, in order to behave [6,186] . Lean production principles seek to eliminate all kinds of waste from the development [7,1]. Ikonen et al declared the adaption of lean methods in software industries to be one of the newest fashions in 2010!…”

Section: Introductionmentioning

confidence: 99%

Efficiency of Software Development after Improvements in Requirements Engineering

Kuhlen¹,

Speck²

2016

IJSEA

View full text Add to dashboard Cite

show abstract

“…Similar metrics were widely adopted in lean manufacturing systems. By revealing waste in projects, significant actionable opportunities in terms of saving resources and accelerating lead-time can be reached for practical use [Ikonen et al, 2010].…”

Section: Agile Team Productivity Measurementmentioning

confidence: 99%

Productivity of agile teams: an empirical evaluation of factors and monitoring processes

Melo¹

View full text Add to dashboard Cite

Lower cost and shorter time-to-market expectations are the major drivers of software productivity improvements. To manage productivity effectively, it is important to identify the most relevant difficulties and develop strategies to cope with them. Agile methods, including Extreme Programming and Scrum, have evolved as approaches to simplify software development process, potentially leading to better productivity. They aim to shorten development time and handle the inevitable changes resulting from market dynamics.Although the industry has extensively adopted agile methods, little research has empirically examined the software development agility construct regarding its dimensions, determinants, and effects on software development performance. Understanding this construct could help determine where to concentrate management efforts (and related financial resources) from a practical standpoint and where to focus research efforts from an academic perspective.Considerable research has been directed at identifying factors that have a significant impact on software development productivity. In general, the studied productivity factors were related to product, personnel, project, process, or organizational issues. Continuously evaluating productivity factors is important, as factors may change under new software engineering practices. However, little research has investigated the major factors influencing agile team productivity.The goal of this thesis was to explore productivity definitions, factors, and monitoring in agile teams and to improve the practice based on the collected evidence and gained knowledge. This thesis presents five novel contributions: C1 -Empirical verification of the importance of productivity for companies adopting agile methods and its perceived benefits; C2 -Rationale for the definition of productivity in the context of agile methods; C3 -Empirical verification of agile team productivity factors; C4 -A conceptual framework for agile team productivity factors and their impact; C5 -A team productivity monitoring process considering adaptability and an evaluation of the usefulness of agile team productivity metrics.

show abstract

Exploring the Sources of Waste in Kanban Software Development Projects

Cited by 32 publications

References 6 publications

Team Portfolio Scrum: An Action Research on Multitasking in Multi-project Scrum Teams

Team Portfolio Scrum: An Action Research on Multitasking in Multi-project Scrum Teams

Efficiency of Software Development after Improvements in Requirements Engineering

Productivity of agile teams: an empirical evaluation of factors and monitoring processes

Contact Info

Product

Resources

About