Kanban benefits and drawbacks

Research Question

What are the expected benefits and drawbacks from Kanban?

Search String

Papers included from the following mapping study: "Kanban in Software Engineering: A Systematic Mapping Study"

Inclusion Criteria

• The same studies included in Kanban in Software Engineering: A Systematic Mapping Study.

Exclusion Criteria

• The same studies included in Kanban in Software Engineering: A Systematic Mapping Study.

• [P18] Scaling Kanban for Software Development in a Multisite Organization: Challenges and Potential Solutions
• Study Type : Observational
• Quality evaluation
• Evidence
• [P9] Going with the flow: An activity theory analysis of flow techniques in software development
• Study Type : Observational
• Quality evaluation
• Evidence
• [P14] On the Impact of Kanban on Software Project Work An Empirical Case Study Investigation
• Study Type : Observational
• Quality evaluation
• Evidence
• [P3] An empirical study of portfolio management and Kanban in agile and lean software companies
• Study Type : Observational
• Quality evaluation
• Evidence
• [P24] Simulating Kanban and Scrum vs. Waterfall with System Dynamics
• Study Type : Randomized Controlled
• Quality evaluation
• Evidence
• [P12] Teaching University Students Kanban with a Collaborative Board Game
• Study Type : Observational
• Quality evaluation
• Evidence
• [P23] Factors Affecting Effectiveness of Agile Usage -- Insights from the BBC Worldwide Case Study
• Study Type : Observational
• Quality evaluation
• Evidence
• [P21] Quantifying the Effect of Using Kanban versus Scrum: A Case Study
• Study Type : Observational
• Quality evaluation
• Evidence
• [P4] Insights into the Perceived Benefits of Kanban in Software Companies: Practitioners' Views
• Study Type : Observational
• Quality evaluation
• Evidence
• [P13] Exploring the Sources of Waste in Kanban Software Development Projects
• Study Type : Observational
• Quality evaluation
• Evidence
• [P2] Student perceptions and attitudes towards the software factory as a learning environment
• Study Type : Observational
• Quality evaluation
• Evidence
• [18] Scaling Kanban for Software Development in a Multisite Organization: Challenges and Potential Solutions
• Study Type : Observational
• Quality evaluation
• Evidence
• [P22] Combining Lean Thinking and Agile Methods for Software Development: A Case Study of a Finnish Provider of Wireless Embedded Systems Detailed
• Study Type : Observational
• Quality evaluation
• Evidence
• [P10] Continuous Software Engineering and Beyond: Trends and Challenges
• Study Type : Observational
• Quality evaluation
• Evidence
• [P16] From Scrum to Kanban: Introducing Lean Principles to a Software Engineering Capstone Course
• Study Type : Non Systematic
• Quality evaluation
• Evidence
• [P11] Combining FOSS and Kanban: An Action Research
• Study Type : Observational
• Quality evaluation
• Evidence
• [P19] From Scrum to Scrumban: A Case Study of a Process Transition
• Study Type : Observational
• Quality evaluation
• Evidence
• [P1] Transition of Software Maintenance Teams from Scrum to Kanban
• Study Type : Observational
• Quality evaluation
• Evidence
• [P20] Developer-driven big-bang process transition from Scrum to Kanban
• Study Type : Observational
• Quality evaluation
• Evidence
• [P15] Whose Experience Do We Care About? Analysis of the Fitness of Scrum and Kanban to User Experience
• Study Type : Observational
• Quality evaluation
• Evidence
• [21] Quantifying the Effect of Using Kanban versus Scrum: A Case Study
• Study Type : Observational
• Quality evaluation
• Evidence
• [23] Factors Affecting Effectiveness of Agile Usage -- Insights from the BBC Worldwide Case Study
• Study Type : Observational
• Quality evaluation
• Evidence
• [P17] Lean software management: BBC Worldwide case study
• Study Type : Observational
• Quality evaluation
• Evidence
• [P5] Kanban for software engineering teaching in a software factory learning environment
• Study Type : Observational
• Quality evaluation
• Evidence

• test
• Evidence based on the paper "[P2] Student perceptions and attitudes towards the software factory as a learning environment"
• Evidence based on the paper "[P4] Insights into the Perceived Benefits of Kanban in Software Companies: Practitioners' Views"
• Evidence based on the paper "[P5] Kanban for software engineering teaching in a software factory learning environment"
• Evidence based on the paper "[P3] An empirical study of portfolio management and Kanban in agile and lean software companies"
• Evidence based on the paper "[P1] Transition of Software Maintenance Teams from Scrum to Kanban"
• Result
• all evidence
• Evidence based on the paper "[P14] On the Impact of Kanban on Software Project Work An Empirical Case Study Investigation"
• Evidence based on the paper "[P2] Student perceptions and attitudes towards the software factory as a learning environment"
• Evidence based on the paper "[P10] Continuous Software Engineering and Beyond: Trends and Challenges"
• Evidence based on the paper "[P5] Kanban for software engineering teaching in a software factory learning environment"
• Evidence based on the paper "[P23] Factors Affecting Effectiveness of Agile Usage -- Insights from the BBC Worldwide Case Study"
• Evidence based on the paper "[P18] Scaling Kanban for Software Development in a Multisite Organization: Challenges and Potential Solutions"
• Evidence based on the paper "[P3] An empirical study of portfolio management and Kanban in agile and lean software companies"
• Evidence based on the paper "[P16] From Scrum to Kanban: Introducing Lean Principles to a Software Engineering Capstone Course"
• Evidence based on the paper "[P4] Insights into the Perceived Benefits of Kanban in Software Companies: Practitioners' Views"
• Evidence based on the paper "[P15] Whose Experience Do We Care About? Analysis of the Fitness of Scrum and Kanban to User Experience"
• Evidence based on the paper "[P21] Quantifying the Effect of Using Kanban versus Scrum: A Case Study"
• Evidence based on the paper "[P11] Combining FOSS and Kanban: An Action Research"
• Evidence based on the paper " [P13] Exploring the Sources of Waste in Kanban Software Development Projects"
• Evidence based on the paper " [P24] Simulating Kanban and Scrum vs. Waterfall with System Dynamics"
• Evidence based on the paper "[P20] Developer-driven big-bang process transition from Scrum to Kanban"
• Evidence based on the paper "[P17] Lean software management: BBC Worldwide case study"
• Evidence based on the paper "[P19] From Scrum to Scrumban: A Case Study of a Process Transition"
• Evidence based on the paper "[P1] Transition of Software Maintenance Teams from Scrum to Kanban"
• Evidence based on the paper "[P9] Going with the flow: An activity theory analysis of flow techniques in software development"
• Evidence based on the paper "[P22] Combining Lean Thinking and Agile Methods for Software Development: A Case Study of a Finnish Provider of Wireless Embedded Systems Detailed"
• Result
• all evidence v2
• Evidence based on the paper "[P14] On the Impact of Kanban on Software Project Work An Empirical Case Study Investigation"
• Evidence based on the paper "[P10] Continuous Software Engineering and Beyond: Trends and Challenges"
• Evidence based on the paper "[P2] Student perceptions and attitudes towards the software factory as a learning environment"
• Evidence based on the paper "[P5] Kanban for software engineering teaching in a software factory learning environment"
• Evidence based on the paper "[P23] Factors Affecting Effectiveness of Agile Usage -- Insights from the BBC Worldwide Case Study"
• Evidence based on the paper "[P18] Scaling Kanban for Software Development in a Multisite Organization: Challenges and Potential Solutions"
• Evidence based on the paper "[P16] From Scrum to Kanban: Introducing Lean Principles to a Software Engineering Capstone Course"
• Evidence based on the paper "[P3] An empirical study of portfolio management and Kanban in agile and lean software companies"
• Evidence based on the paper "[P4] Insights into the Perceived Benefits of Kanban in Software Companies: Practitioners' Views"
• Evidence based on the paper "[P21] Quantifying the Effect of Using Kanban versus Scrum: A Case Study"
• Evidence based on the paper "[P15] Whose Experience Do We Care About? Analysis of the Fitness of Scrum and Kanban to User Experience"
• Evidence based on the paper "[P11] Combining FOSS and Kanban: An Action Research"
• Evidence based on the paper " [P13] Exploring the Sources of Waste in Kanban Software Development Projects"
• Evidence based on the paper " [P24] Simulating Kanban and Scrum vs. Waterfall with System Dynamics"
• Evidence based on the paper "[P20] Developer-driven big-bang process transition from Scrum to Kanban"
• Evidence based on the paper "[P17] Lean software management: BBC Worldwide case study"
• Evidence based on the paper "[P1] Transition of Software Maintenance Teams from Scrum to Kanban"
• Evidence based on the paper "[P19] From Scrum to Scrumban: A Case Study of a Process Transition"
• Evidence based on the paper "[P22] Combining Lean Thinking and Agile Methods for Software Development: A Case Study of a Finnish Provider of Wireless Embedded Systems Detailed"
• Evidence based on the paper "[P9] Going with the flow: An activity theory analysis of flow techniques in software development"
• Result
• teste 2
• Evidence based on the paper "[P11] Combining FOSS and Kanban: An Action Research"
• Evidence based on the paper "[P19] From Scrum to Scrumban: A Case Study of a Process Transition"
• Result
• teste 3
• Evidence based on the paper "[P2] Student perceptions and attitudes towards the software factory as a learning environment"
• Evidence based on the paper "[P11] Combining FOSS and Kanban: An Action Research"
• Evidence based on the paper "[P19] From Scrum to Scrumban: A Case Study of a Process Transition"
• Result

Research question

teste 2

test

all evidence

all evidence v2