QUESt: new practices to represent hypotheses in experiment-driven software development

Recent studies have proposed the use of experiments to guide software development in order to build features that users really want. In this context, product assumptions should be taken as hypotheses to be tested through experiments. User stories (US) are broadly used in the agile context but current guidelines to write them, like INVEST (Independent, Negotiable, Valuable, Estimable, Small and Testable), are not suitable in a experiment-driven...