Minimum Viable Hypothesis

Requirements Management Blogs

In this blog post, James Shore suggests that the concept Minimum Viable Hypothesis should replace the idea of Minimum Viable Product (MVP). His point is that when you focus on the product you could end up being in love with it.

With the Minimum Viable Hypothesis approach, the first step after defining the problem to solve is not to create a minimum viable product, but rather to brainstorm market hypotheses. The important question is “Which groups have the desire and funds for a solution?” You use the build-measure-learn cycle to validate the riskiest assumptions about your market. At the end of the build-measure-learn cycle, you have make the decision to pivot to a new market or persevere. The product is built as a last resort.

software requirements group
Articles Knowledge

Reviewing Requirements for Testability

Modern software development approaches like Agile and Scrum support a strong collaboration between all member of the software development team, software testers and business analysts included. Even if you don’t use a method like Behavior-Driven Development (BDD) or Specification by Example, checking the fact that you will be able to actually test your requirements is […]

Read More
Requirements Management Blogs
Blogs Knowledge

Find Missing Requirements

This blog post by Betsy Stockdale explains how to use the Feature Tree model to discover missing requirements.

Read More
Requirements Management Blogs
Blogs Knowledge

Perfect Requirements

In this blog post, James Christie starts from the fact that perfect requirements don’t exist to discuss the idea that the quality of requirements is directly influenced by the time and money you invest in crafting them.

Read More

Copyright © 2009-2022 Martinig & Associates