TY  - CHAP
U1  - Konferenzveröffentlichung
A1  - Münch, Jürgen
A1  - Fagerholm, Fabian
A1  - Sanchez Guinea, Alejandro
A1  - Mäenpää, Hanna
ED  - Jürjens, Jan
T1  - The RIGHT model for continuous experimentation
T2  - Software Engineering 2017 : Tagung vom 21. - 24. Februar 2017 in Hannover. - (GI-Edition / proceedings ; 267)
N2  - Due to rapidly changing technologies and business contexts, many products and services are developed under high uncertainties. It is often impossible to predict customer behaviors and outcomes upfront. Therefore, product and service developers must continuously find out what customers want, requiring a more experimental mode of management and appropriate support for continuously conducting experiments. We have analytically derived an initial model for continuous experimentation from prior work and matched it against empirical case study findings from two startup companies. We examined the preconditions for setting up an experimentation system for continuous customer experiments. The resulting RIGHT model for Continuous Experimentation (Rapid Iterative value creation Gained through High-frequency Testing) illustrates the building blocks required for such a system and the necessary infrastructure. The major findings are that a suitable experimentation system requires the ability to design, manage, and conduct experiments, create so-called minimum viable products or features, 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 integration of experiment results in the product development cycle, software development process, and business strategy. This summary refers to the article The RIGHT Model for Continuous Experimentation, published in the Journal of Systems and Software [Fa17].
KW  - continuous experimentation
KW  - product development
KW  - lean startup
KW  - software development process
KW  - agile software development
KW  - hypothesis-driven software development
Y1  - 2017
U6  - http://nbn-resolving.de/urn/resolver.pl?urn:nbn:de:bsz:rt2-opus4-16638
UN  - http://nbn-resolving.de/urn/resolver.pl?urn:nbn:de:bsz:rt2-opus4-16638
SP  - 89
EP  - 90
S1  - 2
PB  - Gesellschaft für Informatik
CY  - Bonn
ER  - 
TY  - JOUR
U1  - Zeitschriftenartikel, wissenschaftlich - begutachtet (reviewed)
A1  - Fagerholm, Fabian
A1  - Sanchez Guinea, Alejandro
A1  - Mäenpää, Hanna
A1  - Münch, Jürgen
T1  - The RIGHT model for continuous experimentation
JF  - The journal of systems and software : JSS
N2  - 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.
KW  - continuous experimentation
KW  - product development
KW  - software architecture
KW  - software development process
KW  - agile software development
KW  - lean software development
Y1  - 2017
SN  - 0164-1212
SS  - 0164-1212
U6  - https://dx.doi.org/10.1016/j.jss.2016.03.034
DO  - https://dx.doi.org/10.1016/j.jss.2016.03.034
VL  - 123
SP  - 292
EP  - 305
S1  - 14
PB  - Elsevier
CY  - Amsterdam
ER  -