Kanban in software engineering: A systematic mapping study

Abstract Following a well-established track record of success in other domains such as manufacturing, Kanban is increasingly used to achieve continuous development and delivery of value in the software industry. However, while research on Kanban in software is growing, these articles are largely descriptive, and there is limited rigorous research on its application and with little cohesive building of cumulative knowledge. As a result, it is extremely difficult to determine the true value of Kanban in software engineering. This study investigates the scientific evidence to date regarding Kanban by conducting a systematic mapping of Kanban literature in software engineering between 2006 and 2016. The search strategy resulted in 382 studies, of which 23 were identified as primary papers relevant to this research. This study is unique as it compares the findings of these primary papers with insights from a review of 23 Kanban experience reports during the same period. This study makes four important contributions, (i) a state-of-the-art of Kanban research is provided, (ii) the reported benefits and challenges are identified in both the primary papers and experience reports, (iii) recommended practices from both the primary papers and experience reports are listed and (iv) opportunities for future Kanban research are identified.

[1]  Gaetano Mazzanti Agile in the Bathtub: Developing and Producing Bathtubs the Agile Way , 2012, 2012 Agile Conference.

[2]  Marko Taipale Huitale - A Story of a Finnish Lean Startup , 2010, LESS.

[3]  Christopher S Kim,et al.  Implementation of lean thinking: one health system's journey. , 2009, Joint Commission journal on quality and patient safety.

[4]  James Miller,et al.  The kanban approach, between agility and leanness: a systematic review , 2014, Empirical Software Engineering.

[5]  Pasi Kuvaja,et al.  Combining Lean Thinking and Agile Methods for Software Development: A Case Study of a Finnish Provider of Wireless Embedded Systems Detailed , 2014, 2014 47th Hawaii International Conference on System Sciences.

[6]  C. Sendil Kumar,et al.  Literature review of JIT-KANBAN system , 2007 .

[7]  Chris F. Kemerer,et al.  The assimilation of software process innovations: an organizational learning perspective , 1997 .

[8]  Pekka Abrahamsson,et al.  ‘Lots done, more to do’: the current state of agile systems development research , 2009, Eur. J. Inf. Syst..

[9]  Mira Kajko-Mattsson,et al.  From scrum to scrumban: A case study of a process transition , 2012, 2012 International Conference on Software and System Process (ICSSP).

[10]  Pär J. Ågerfalk,et al.  Systems Development Method Rationale: A Conceptual Framework for Analysis , 2003, ICEIS.

[11]  Claes Wohlin,et al.  Experimentation in Software Engineering , 2012, Springer Berlin Heidelberg.

[12]  Gareth Evans,et al.  Factors Affecting Effectiveness of Agile Usage - Insights from the BBC Worldwide Case Study , 2011, XP.

[13]  Kieran Conboy,et al.  Agility from First Principles: Reconstructing the Concept of Agility in Information Systems Development , 2009, Inf. Syst. Res..

[14]  Kai Petersen,et al.  Guidelines for conducting systematic mapping studies in software engineering: An update , 2015, Inf. Softw. Technol..

[15]  Steve Neely,et al.  Continuous Delivery? Easy! Just Change Everything (Well, Maybe It Is Not That Easy) , 2013, 2013 Agile Conference.

[16]  Michael J. Gallivan,et al.  Organizational adoption and assimilation of complex technological innovations: development and application of a new framework , 2001, DATB.

[17]  Christopher M. Shinkle Applying the Dreyfus Model of Skill Acquisition to the Adoption of Kanban Systems at Software Engineering Professionals (SEP) , 2009, 2009 Agile Conference.

[18]  Judy McKay,et al.  How well do we understand boundary practices? empirical evidence from a practice of business analysts , 2011, ECIS.

[19]  Oisín Cawley,et al.  "Leagile" software development: An experience report analysis of the application of lean approaches in agile software development , 2012, J. Syst. Softw..

[20]  Daniel Roos,et al.  The machine that changed the world : the story of lean production , 1991 .

[21]  S. Godsill,et al.  The Institution of Engineering and Technology Seminar on Target Tracking and Data Fusion , 2008 .

[22]  Danny Berry,et al.  Leagility: Integrating the lean and agile manufacturing paradigms in the total supply chain , 1999 .

[23]  Peter Middleton,et al.  Lean Software Management: BBC Worldwide Case Study , 2012, IEEE Transactions on Engineering Management.

[24]  Michele Marchesi,et al.  Studying Lean-Kanban Approach Using Software Process Simulation , 2011, XP.

[25]  Cecilia Fernandes There and Back Again: From Iterative to Flow ... and Back to Iterative! , 2012, 2012 Agile Conference.

[26]  Kalle Lyytinen,et al.  Information system development agility as organizational learning , 2006, Eur. J. Inf. Syst..

[27]  C. Argyris Single-loop and double-loop models in research on decision making. , 1976 .

[28]  Kai Petersen,et al.  Systematic Mapping Studies in Software Engineering , 2008, EASE.

[29]  Ken Power Definition of Ready: An Experience Report from Teams at Cisco , 2014, XP.

[30]  Thushara Wijewardena Do You Dare to Ask Your HR Manager to Practice KANBAN? The Experience Report of an Offshore Software Company in Sri Lanka Introducing Agile Practices into its Human Resource (HR) Department , 2011, 2011 AGILE Conference.

[31]  T. Melton,et al.  The Benefits of Lean Manufacturing: What Lean Thinking has to Offer the Process Industries , 2005 .

[32]  Corey Ladas,et al.  Scrumban: Essays on Kanban Systems for Lean Software Development , 2009 .

[33]  Katarzyna Terlecka,et al.  Combining Kanban and Scrum -- Lessons from a Team of Sysadmins , 2012, 2012 Agile Conference.

[34]  Mary Shaw,et al.  Writing good software engineering research papers , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[35]  Claes Wohlin,et al.  Measuring the flow in lean software development , 2011, Softw. Pract. Exp..

[36]  Muhammad Ovais Ahmad,et al.  Scaling Kanban for Software Development in a Multisite Organization: Challenges and Potential Solutions , 2015, XP.

[37]  新郷 重夫,et al.  A study of the Toyota production system from an industrial engineering viewpoint , 1989 .

[38]  K. Lyytinen,et al.  Exploring the intellectual structures of information systems development: A social action theoretic analysis , 1996 .

[39]  Maarit Laanti,et al.  Agile and Wellbeing -- Stress, Empowerment, and Performance in Scrum and Kanban Teams , 2013, 2013 46th Hawaii International Conference on System Sciences.

[40]  Y. Sugimori,et al.  Toyota production system and Kanban system Materialization of just-in-time and respect-for-human system , 1977 .

[41]  Jeffrey K. Liker,et al.  The Toyota way : 14 management principles from the world's greatest manufacturer , 2004 .

[42]  KitchenhamBarbara,et al.  A systematic review of systematic review process research in software engineering , 2013 .

[43]  Standard Glossary of Software Engineering Terminology , 1990 .

[44]  Maarit Laanti,et al.  Is Agile Portfolio Management Following the Principles of Large-Scale Agile? Case Study in Finnish Broadcasting Company Yle , 2015, 2015 Agile Conference.

[45]  David W. Bustard,et al.  Smoothing the Transition from Agile Software Development to Agile Software Maintenance , 2016, XP.

[46]  Osamu Kimura,et al.  Desiǵn and analysis of Pull System, a method of multi-staǵe production control , 1981 .

[47]  Fumihiko Kinoshita Practices of an Agile Team , 2008, Agile 2008 Conference.

[48]  Philipp Nadel,et al.  The Machine That Changed The World , 2016 .

[49]  Muhammad Ovais Ahmad,et al.  An empirical study of portfolio management and Kanban in agile and lean software companies , 2017, J. Softw. Evol. Process..

[50]  Muhammad Ovais Ahmad,et al.  Transition of Software Maintenance Teams from Scrum to Kanban , 2016, 2016 49th Hawaii International Conference on System Sciences (HICSS).

[51]  Kieran Conboy,et al.  A Metric-Based Approach to Managing Architecture-Related Impediments in Product Development Flow: An Industry Case Study from Cisco , 2015, 2015 IEEE/ACM 2nd International Workshop on Software Architecture and Metrics.

[52]  M. Venables Boeing: going for lean [lean manufacturing] , 2005 .

[53]  D. Reinertsen The Principles of Product Development Flow: Second Generation Lean Product Development , 2009 .

[54]  Michele Marchesi,et al.  Simulating Kanban and Scrum vs. Waterfall with System Dynamics , 2011, XP.

[55]  Pearl Brereton,et al.  Performing systematic literature reviews in software engineering , 2006, ICSE.

[56]  Kai Petersen,et al.  Waste and Lead Time Reduction in a Software Product Customization Process with Value Stream Maps , 2010, 2010 21st Australian Software Engineering Conference.

[57]  Laurie A. Williams,et al.  What agile teams think of agile principles , 2012, Commun. ACM.

[58]  H. K. Raju,et al.  Kanban Pull and Flow — A transparent workflow for improved quality and productivity in software developmet , 2013, ARTCom 2013.

[59]  Filippo Eros Pani,et al.  A Review of Lean-Kanban Approaches in the Software Development , 2013 .

[60]  Michele Marchesi,et al.  Simulation of software maintenance process, with and without a work‐in‐process limit , 2013, J. Softw. Evol. Process..

[61]  Karen Greaves,et al.  Taming the Customer Support Queue: A Kanban Experience Report , 2011, 2011 AGILE Conference.

[62]  Michael A. Cusumano,et al.  Lean Software Development: A Tutorial , 2012, IEEE Software.

[63]  Pearl Brereton,et al.  A systematic review of systematic review process research in software engineering , 2013, Inf. Softw. Technol..

[64]  D. Wastell,et al.  The behavioral dynamics of information system development: A stress perspective , 1993 .

[65]  Muhammad Ovais Ahmad,et al.  Kanban in software development: A systematic literature review , 2013, 2013 39th Euromicro Conference on Software Engineering and Advanced Applications.

[66]  Tony Gorschek,et al.  Evaluation and Measurement of Software Process Improvement—A Systematic Literature Review , 2012, IEEE Transactions on Software Engineering.

[67]  Paul Shannon,et al.  From Chaos to Kanban, via Scrum , 2010, XP.

[68]  Per Runeson,et al.  Guidelines for conducting and reporting case study research in software engineering , 2009, Empirical Software Engineering.

[69]  Muhammad Ovais Ahmad,et al.  Comparing Requirements Decomposition Within the Scrum, Scrum with Kanban, XP, and Banana Development Processes , 2017, XP.

[70]  Marc Gravel,et al.  Using the Kanban in a job shop environment , 1988 .

[71]  Mary Poppendieck,et al.  Lean Software Development: An Agile Toolkit , 2003 .

[72]  Robert L. Nord,et al.  Making Architecture Visible to Improve Flow Management in Lean Software Development , 2012, IEEE Software.

[73]  Daniel R. Greening Enterprise Scrum: Scaling Scrum to the Executive Level , 2010, 2010 43rd Hawaii International Conference on System Sciences.

[74]  Olav Maassen,et al.  Kanban at an Insurance Company (Are You Sure?) , 2010, XP.

[75]  Linton L. S. Chai,et al.  e-based inter-enterprise supply chain Kanban for demand and order fulfilment management , 2008, 2008 IEEE International Conference on Emerging Technologies and Factory Automation.

[76]  Andrew Kusiak,et al.  Overview of Kanban systems , 1996 .

[77]  Pekka Abrahamsson,et al.  On the Impact of Kanban on Software Project Work: An Empirical Case Study Investigation , 2011, 2011 16th IEEE International Conference on Engineering of Complex Computer Systems.

[78]  Carl Adams Managing crowdsourcing assignments , 2011 .

[79]  M. Christopher,et al.  The Supply Chain Strategy Conundrum: To be Lean Or Agile or To be Lean And Agile? , 2002 .

[80]  Ryan Polk Agile and Kanban in Coordination , 2011, 2011 AGILE Conference.

[81]  J. J. Zang A Never Ending Battle for Continuous Improvement , 2011, XP.

[82]  Mary Poppendieck,et al.  Lean Software Development , 2007, 29th International Conference on Software Engineering (ICSE'07 Companion).

[83]  JoAnne Yates,et al.  It's About Time: Temporal Structuring in Organizations , 2002, Organ. Sci..

[84]  Mira Kajko-Mattsson,et al.  Developer-driven big-bang process transition from Scrum to Kanban , 2011, ICSSP '11.

[85]  Dean Leffingwell,et al.  Agile Software Requirements: Lean Requirements Practices for Teams, Programs, and the Enterprise , 2011 .

[86]  Michel Evaristo Febles Parker,et al.  The Agile Management of Development Projects of Software Combining Scrum, Kanban and Expert Consultation , 2014, OSS.

[87]  Pearl Brereton,et al.  Systematic literature reviews in software engineering - A tertiary study , 2010, Inf. Softw. Technol..

[88]  Jürgen Börstler,et al.  The impacts of agile and lean practices on project constraints: A tertiary study , 2016, J. Syst. Softw..

[89]  Mary Poppendieck,et al.  Implementing Lean Software Development: From Concept to Cash (The Addison-Wesley Signature Series) , 2006 .

[90]  Claes Wohlin,et al.  A comparison of issues and advantages in agile and incremental development between state of the art and an industrial case , 2009, J. Syst. Softw..

[91]  Per Runeson,et al.  Early identification of bottlenecks in very large scale system of systems software development , 2014, J. Softw. Evol. Process..

[92]  Maurice Landry,et al.  Can the field of MIS be disciplined? , 1989, CACM.

[93]  A. Hui,et al.  Lean Change: Enabling Agile Transformation through Lean Startup, Kotter and Kanban: An Experience Report , 2013, 2013 Agile Conference.

[94]  Denis Dennehy,et al.  Going with the flow: An activity theory analysis of flow techniques in software development , 2017, J. Syst. Softw..

[95]  Helena Szczerbicka,et al.  Modeling and optimization of kanban controlled manufacturing systems with GSPN including QN , 1998, SMC'98 Conference Proceedings. 1998 IEEE International Conference on Systems, Man, and Cybernetics (Cat. No.98CH36218).

[96]  Eric R. Willeke The Inkubook Experience: A Tale of Five Processes , 2009, 2009 Agile Conference.

[97]  Tony Gorschek,et al.  Software development in startup companies: A systematic mapping study , 2014, Inf. Softw. Technol..

[98]  Marko Seikola,et al.  Kanban Implementation in a Telecom Product Maintenance , 2011, 2011 37th EUROMICRO Conference on Software Engineering and Advanced Applications.

[99]  N. Tokatli Global sourcing: insights from the global clothing industry—the case of Zara, a fast fashion retailer , 2007 .

[100]  Agneta Olerup Design Approaches: A Comparative Study of Information System Design and Architecutral Design , 1991, Comput. J..

[101]  Taiichi Ohno,et al.  Toyota Production System : Beyond Large-Scale Production , 1988 .

[102]  Dag I. K. Sjøberg,et al.  Quantifying the Effect of Using Kanban versus Scrum: A Case Study , 2012, IEEE Software.

[103]  Pearl Brereton,et al.  Using mapping studies as the basis for further research - A participant-observer case study , 2011, Inf. Softw. Technol..

[104]  Pekka Abrahamsson,et al.  Lean Software Development , 2012, IEEE Softw..

[105]  Jørn Ola Birkeland From a Timebox Tangle to a More Flexible Flow , 2010, XP.

[106]  Mary Poppendieck,et al.  Leading Lean Software Development: Results Are Not the Point , 2009 .

[107]  Tore Dybå,et al.  Empirical studies of agile software development: A systematic review , 2008, Inf. Softw. Technol..

[108]  J. Pettit,et al.  Development and the Learning Organisation: An introduction , 2002 .

[109]  Henrik Kniberg,et al.  Kanban and Scrum - Making the Most of Both , 2010 .

[110]  E. Schein Culture: The Missing Concept in Organization Studies. , 1996 .