Implementing hypothesis-driven development
A risk in software development is that teams are so busy creating more and more features that they forget to reflect upon their business value, while everyone knows that not every feature is a success. Some features may not be used at all, or may even be disliked by users. As an industry, we have come to learn that product owners have a hard time predicting which features will be liked by users and which will not. Even when using all of the feedback mechanisms discussed previously, predicting what users want is difficult.
Another important thing to recognize is that every feature in the product also brings a future cost. Every feature requires documentation, support, and maintenance. This means that unnecessary features are driving costs up as well. From this perspective, it makes sense to not only leave non-value features but to even remove them from the product as soon as possible.
Hypothesis-driven development is a practice that starts...