From Opinions to Data-Driven Software R&D: A Multi-case Study on How to Close the 'Open Loop' Problem

In most software development companies the road mapping and requirements prioritization process is a complex process in which product management experiences difficulties in getting timely and accurate customer feedback. The feedback loop from customers is slow and often there is a lack of mechanisms that allow for efficient customer data collection and analysis. As a result, there is the risk that requirements prioritization becomes opinion-based rather than data-driven, and that R&D investments are made without an accurate way of continuously validating whether they correspond to customer needs. We call this phenomenon the 'open loop' problem, referring to the challenges for product management to get accurate and timely feedback from customers. To address this problem, we develop the HYPEX model (Hypothesis Experiment Data-Driven Development) that supports companies in running feature experiments to shorten customer feedback loops. We evaluate the model in three software development companies and observe how feature experiments increase the opportunity for data-driven software development.

[1]  Geoff Walsham,et al.  Interpretive case studies in IS research: nature and method , 1995 .

[2]  J. Whitney Case Study Research , 1999 .

[3]  Eric Ries,et al.  The lean startup : how constant innovation creates radically successful businesses , 2011 .

[4]  R. Yin Case Study Research: Design and Methods , 1984 .

[5]  Jan Bosch,et al.  Building Products as Innovation Experiment Systems , 2012, ICSOB.

[6]  Jan Bosch,et al.  Post-deployment Data Collection in Software-Intensive Embedded Products , 2013, Continuous Software Engineering.

[7]  Joseph A. Maxwell,et al.  Qualitative Research Design: An Interactive Approach , 1996 .

[8]  Craig Larman,et al.  Scaling Lean & Agile Development: Thinking and Organizational Tools for Large-Scale Scrum , 2008 .

[9]  Jan Bosch,et al.  Towards Data-Driven Product Development: A Multiple Case Study on Post-deployment Data Usage in Software-Intensive Embedded Systems , 2013, LESS.

[10]  Jan Bosch,et al.  Post-deployment Data Collection in Software-Intensive Embedded Products , 2013, ICSOB.

[11]  Karen Skibba Book Review: Qualitative Research Design: An Interactive Approach (2nd ed.) , 2006 .

[12]  Barry W. Boehm,et al.  Value-based software engineering: reinventing , 2003, SOEN.

[13]  Steve Blank The Four Steps to the Epiphany: Successful Strategies for Products that Win , 2013 .

[14]  Jez Humble,et al.  Continuous Delivery: Reliable Software Releases Through Build, Test, and Deployment Automation , 2010 .

[15]  Jan Bosch,et al.  Eternal Embedded Software: Towards Innovation Experiment Systems , 2012, ISoLA.

[16]  Alistair Cockburn,et al.  Agile Software Development: The Business of Innovation , 2001, Computer.

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

[18]  Jan Bosch,et al.  Climbing the "Stairway to Heaven" -- A Mulitiple-Case Study Exploring Barriers in the Transition from Agile Development towards Continuous Deployment of Software , 2012, 2012 38th Euromicro Conference on Software Engineering and Advanced Applications.

[19]  Christian Bird,et al.  Empirical software engineering at Microsoft Research , 2011, CSCW.

[20]  Pekka Abrahamsson,et al.  New directions on agile methods: a comparative analysis , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[21]  Raymond J. Madachy,et al.  Integrated Modeling of Business Value and Software Processes , 2005, ISPW.

[22]  Ron Kohavi,et al.  Online Experimentation at Microsoft , 2009 .