The RIGHT model for continuous experimentation

  • Context: Development of software intensive products and services increasingly occurs by continuously deploying product or service increments, such as new features and enhancements, to customers. Product and service developers must continuously find out what customers want by direct customer feedback and usage behaviour observation. Objective: This paper examines the preconditions for setting up an experimentation system for continuous customer experiments. It describes the RIGHT model for Continuous Experimentation (Rapid Iterative value creation Gained through High-frequency Testing), illustrating the building blocks required for such a system. Method: An initial model for continuous experimentation is analytically derived from prior work. The model is matched against empirical case study findings from two startup companies and further developed. Results: Building blocks for a continuous experimentation system and infrastructure are presented. Conclusions: A suitable experimentation system requires at least the ability to release minimum viable products or features with suitable instrumentation, design and manage experiment plans, link experiment results with a product roadmap, and manage a flexible business strategy. The main challenges are proper, rapid design of experiments, advanced instrumentation of software to collect, analyse, and store relevant data, and the integration of experiment results in both the product development cycle and the software development process.

Download full text files

  • 1569.pdf
    eng

Export metadata

Additional Services

Share in Twitter Search Google Scholar
Metadaten
Name:Münch, Jürgen
DOI:https://doi.org/10.1016/j.jss.2016.03.034
ISSN:0164-1212
Erschienen in:The journal of systems and software : JSS
Publisher:Elsevier
Place of publication:Amsterdam
Document Type:Article
Language:English
Year of Publication:2017
Tag:agile software development; continuous experimentation; lean software development; product development; software architecture; software development process
Volume:123
Pagenumber:14
First Page:292
Last Page:305
Dewey Decimal Classification:004 Informatik
Open Access:Nein
Licence (German):License Logo  Lizenzbedingungen Elsevier