Minimum Marketable Product: Revolutionizing the Way You Develop and Launch Products

Do Less on Timing The Market

In the Scrum Guide, we are trained to deliver potentially-releasable products early and frequently to collect user feedbacks; adapt ourselves during the process. However, in real scenarios, many organizations tend to do long-term survey to predict whether their ideas are valuable and decide to invest resources on them.

The reason for market prediction is avoid huge loss when a product is published, but time cost is usually neglected during the process. Instead, we strongly suggest a Scrum team to adapt to, rather than forecast, variable environments.

Do less on timing the market; do more on adapting to the market

Minimum Marketable Product

I still freshly remembered that 2 months ago, our team was required to deliver a new feature: Grid-Trading Bot, which was similar to the product Pionex had released. And I had to ask our team to demonstrate selected product backlogs at sprint reviews to guarantee our deliverables could meet the timeline. In fact, we don’t know whether our clients would buy into the feature since there have been similar products on the market, and we cannot foresee FTX’s breaking…