MoSCoW - Formalisation of MVP - Prioritization in Practice

If you have ever been involved in launching a digital product, you've probably encountered the situation: deadlines are tight, resources are limited, and the list of desired features is growing like a snowball. The customer wants “everything at once,” the development team warns about risks, and the team is left wondering: where do we start? The answer is, of course, with the MVP! But intuition alone is often not enough to define it — and that’s when prioritization techniques come to the rescue.

So, in this workshop, we will practise one of the prioritization techniques for a test task and find the right balance for truly key features in MVP. To do this, we will briefly review the theory and go through 10 simple steps to understand what is an MVP and what is not.

P.S. MoSCoW (Must have, Should have, Could have, Won’t have) is one of the fastest ways of initial sorting. It is suitable for teams just starting work on an MVP or conducting a quick assessment.