Extending value stream mapping through waste definition beyond customer perspective

Value stream mapping (VSM) is one of the several Lean practices, which has recently attracted interest in the software engineering community. In other contexts (such as military, health and production), VSM has achieved considerable improvements in processes and products. The goal is to capitalize on these benefits in the software intensive product development context. The primary contribution is that we are extending the definition of waste to fit in the software intensive product development context. As traditionally in VSM everything that is not considered valuable is waste, we do this practically by looking at value beyond the customer perspective and using the software value map. An evaluation has been conducted through an industrial case study. First, the instantiation and motivations for selecting certain strategies have been provided. Second, the outcome of the VSM is described in detail. The instantiation of VSM via workshops was considered good as workshops allowed active interaction and discussion stakeholders' groups that are distant from each other in the regular work. With respect to waste and improvement identification, the participants were able to identify similar improvement suggestions. In a retrospective, the value stream approach was perceived positively by the practitioners with respect to process and outcome. Copyright © 2014 John Wiley & Sons, Ltd.

[1]  Kai Petersen An Empirical Study of Lead-Times in Incremental and Agile Software Development , 2010, ICSP.

[2]  J. Morse Designing funded qualitative research. , 1994 .

[3]  R. Dorf,et al.  The Balanced Scorecard: Translating Strategy Into Action , 1997, Proceedings of the IEEE.

[4]  Colin Robson,et al.  Real World Research: A Resource for Social Scientists and Practitioner-Researchers , 1993 .

[5]  John R. Shook,et al.  Learning to See: Value Stream Mapping to Create Value and , 1998 .

[6]  Chandandeep Grewal,et al.  An initiative to implement lean manufacturing using value stream mapping in a small company , 2008, Int. J. Manuf. Technol. Manag..

[7]  David Raffo,et al.  Providing value to customers in software development through lean principles , 2008, Softw. Process. Improv. Pract..

[8]  Dean Leffingwell,et al.  Managing software requirements: a unified approach , 1999 .

[9]  Cem Kaner,et al.  Foundations of Software Testing , 2013 .

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

[11]  大野 耐一,et al.  Toyota production system : beyond large-scale production , 1988 .

[12]  Claes Wohlin,et al.  Software process improvement through the Lean Measurement (SPI-LEAM) method , 2010, J. Syst. Softw..

[13]  Jim Chase,et al.  Value creation in the product development process , 2001 .

[14]  M. Waters,et al.  Journey to lean [lean practices in aerospace product development] , 2005 .

[15]  Claes Wohlin,et al.  The Waterfall Model in Large-Scale Development , 2009, PROFES.

[16]  Kai Petersen,et al.  Worldviews, Research Methods, and their Relationship to Validity in Empirical Software Engineering Research , 2013, 2013 Joint Conference of the 23rd International Workshop on Software Measurement and the 8th International Conference on Software Process and Product Measurement.

[17]  Paramdeep Singh,et al.  Application of Lean Tool (Value Stream Mapping) in Minimisation of the Non-Value Added Waste (A Case Study of Tractor Industry) , 2011 .

[18]  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..

[19]  Kai Petersen,et al.  Is Lean Agile and Agile Lean?: A Comparison between Two Software Development Paradigms , 2011 .

[20]  Per Runeson,et al.  Case Studies Synthesis: Brief Experience and Challenges for the Future , 2011, 2011 International Symposium on Empirical Software Engineering and Measurement.

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

[22]  Tony Gorschek,et al.  The software value map — an exhaustive collection of value aspects for the development of software intensive products , 2013, J. Softw. Evol. Process..

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

[24]  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..

[25]  William E. Trischler Understanding and Applying Value-Added Assessment: Eliminating Business Process Waste , 1996 .

[26]  Kai Petersen,et al.  Measuring and predicting software productivity: A systematic map and review , 2011, Inf. Softw. Technol..

[27]  Nick Rich,et al.  Value stream mapping , 1999 .

[28]  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.

[29]  Claes Wohlin,et al.  The effect of moving from a plan-driven to an incremental software development approach with agile practices , 2010, Empirical Software Engineering.

[30]  Daniela E. Damian,et al.  Selecting Empirical Methods for Software Engineering Research , 2008, Guide to Advanced Empirical Software Engineering.

[31]  Mike Sullivan,et al.  The Art of Lean Software Development: A Practical and Incremental Approach , 2009 .

[32]  David Raffo,et al.  Providing value to customers in software development through lean principles , 2008 .

[33]  Hugh McManus Product Development Value Stream Mapping (PDVSM) Manual Release 1.0 , 2005 .

[34]  Anjani Kumar,et al.  The Effect of Lean Manufacturing on Product Quality and Industrial Productivity: AnEmpirical Survey , 2009 .

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

[36]  Christine Nadel,et al.  Case Study Research Design And Methods , 2016 .

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

[38]  Blair McCallum,et al.  Journey to lean , 2004 .

[39]  D. Ross Jeffery,et al.  Misleading Metrics and Unsound Analyses , 2007, IEEE Software.

[40]  Claes Wohlin,et al.  Context in industrial software engineering research , 2009, 2009 3rd International Symposium on Empirical Software Engineering and Measurement.

[41]  S. Vinodh,et al.  QFD integrated value stream mapping: an enabler of lean manufacturing , 2011 .

[42]  John K. Gershenson,et al.  The Application of Value Stream Mapping to Lean Engineering , 2004 .

[43]  Claes Wohlin,et al.  Experimentation in software engineering: an introduction , 2000 .

[44]  Nick Rich,et al.  The seven value stream mapping tools , 1997 .

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

[46]  Ricardo Valerdi,et al.  Synthesizing SoS concepts for use in cost modeling , 2007, Syst. Eng..

[47]  Laura Johnson,et al.  How Many Interviews Are Enough? , 2006 .

[48]  Tina Agustiady A Lean Six Sigma Case Study , 2013 .

[49]  Tony Gorschek,et al.  Packaging software process improvement issues: a method and a case study , 2004, Softw. Pract. Exp..

[50]  R. Kaplan,et al.  The balanced scorecard--measures that drive performance. , 2015, Harvard business review.

[51]  James P. Womack,et al.  Lean Thinking: Banish Waste and Create Wealth in Your Corporation , 1996 .

[52]  Jeffrey K. Liker,et al.  The Toyota Product Development System: Integrating People, Process And Technology , 2006 .