When scoping an MVP is worth the effort

There is no clever trick in this one, just a handful of decisions worth making deliberately. Scoping an MVP is not free, and pretending otherwise leads to bad decisions.

Clear scope protects the client at least as much as it protects the agency. It is the sort of thing that looks like polish right up until it costs you an enquiry.

When it is worth it

Minimum means uncomfortable, viable means it works. The cost of getting this wrong is rarely visible on the day it happens. Anything you cannot measure here, you are deciding by taste, which is fine as long as everyone knows it.

When it is not

If nothing downstream depends on it and nobody is complaining, it can wait. The reasoning matters more than the rule, because the rule has exceptions.

How to decide

The point is to learn something specific. The reasoning matters more than the rule, because the rule has exceptions. The teams that stay on top of it are the ones who put it on a calendar rather than a wish list.

What this looks like day to day

The projects that go badly are rarely the ones with the hardest technical problems. Three things worth confirming about scoping an MVP before you move on:

• Someone can say what the current setup is without going to look
• The point is to learn something specific — and you know whether that is true here
• There is a way to tell whether the last change to this helped

None of this needs a rewrite. Most of it is a morning's work once someone decides to do it.