Share

Most software projects aim to release a minimum viable product (MVP), or a similar concept. We often see MVP specifications that are extremely complex, almost matching the vision of the ultimate product.

The mistake here is thinking in terms of absolute importance. If we ask ourselves ‘is this important’, the answer is often ‘yes’.

A better approach is to rank features in terms of their relative importance. Then go through the list asking yourself ’if I was given the choice to either release the product now or wait another two months to deliver the additional feature, which would I choose?’.

Complexity and risk don’t increase linearly with the number of things you want your MVP to do. This is easy to neglect when planning. A simple MVP is the best remedy.

Want to scale up your IoT solution?

Get in touch today to set up a preliminary discussion with our IoT wireless mesh experts to improve your position for the future.