There is a need in many software-based companies to evolve their software development practices towards continuous integration and continuous deployment. This allows a company to frequently and rapidly integrate and deploy their work and in consequence also opens opportunities for getting feedback from customers on a regular basis. Ideally, this feedback is used to support design decisions early in the development process, e.g., to determine which features should be maintained over time and which features should be skipped. In more general terms, the entire R&D system of an organization should be in a state where it is able to respond and act quickly based in instant customer feedback and where actual deployment of software functionality is seen as a way of fast experimenting and testing what the customer needs. Experimentation refers here to fast validation of a business model or more specifically validating a value hypothesis. Reaching such a state of continuous experimentation implies a lot of challenges for organizations. Selected challenges are how to develop the “right” software while developing software “right”, how to have an appropriate tool infrastructure in place, how to measure and evaluate customer value, what are appropriate feedback systems, how to improve the velocity of software development, how to increase the business hit rate with new products and features, how to integrate such experiments into the development process, how to link knowledge about value for users or customers to higher-level goals of an organization. These challenges are quite new for many software-based organizations and not sufficiently understood from a software engineering
[1]
Annie I. Antón,et al.
Goal-based requirements analysis
,
1996,
Proceedings of the Second International Conference on Requirements Engineering.
[2]
Michael Vitale,et al.
The Wisdom of Crowds
,
2015,
Cell.
[3]
Annie I. Antón,et al.
Point/Counterpoint: Don't Solve a Problem Before You Get to It / Successful Software Projects Need Requirements Planning
,
2003,
IEEE Softw..
[4]
Eric S. K. Yu,et al.
Towards modelling and reasoning support for early-phase requirements engineering
,
1997,
Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.
[5]
Axel van Lamsweerde,et al.
From Object Orientation to Goal Orientation: A Paradigm Shift for Requirements Engineering
,
2002,
RISSEF.
[6]
Ioannis Stamelos,et al.
Agile Software Development Quality Assurance
,
2007
.
[7]
A. van Lamsweerde.
Goal-oriented requirements enginering: a roundtrip from research to practice [enginering read engineering]
,
2004
.
[8]
Evangelia Kavakli,et al.
Goal-Oriented Requirements Engineering: A Unifying Framework
,
2002,
Requirements Engineering.