Using MVP in Scrum and what is the Minimum viable product (MVP)

MVP means Minimum viable product and although this is a product concept, Scrum teams need to know exactly what MVP is.

To think about MVP, one of the most important things is to look at the product (idea) as a whole and assess its real applicability. This is not a thorough analysis, but the most significant assessment, so that we can generally imagine what the product looks like at first glance – in our case: the online platform.

The ideas you sent me to show true professionalism and a deep understanding of the subject – almost everything has been thought out. Naturally, speaking of scruples, such an initial detail is not only frightening and superfluous but even useless.

Why? – you may be wondering, doesn’t it help us how detailed everything is invented and that we are only asked to follow it, develop it further, try it out and release it? The answer is no. As you already know, scrum is an adaptive and adaptive process that is flexible and open to change.

The important thing about scrum is to determine the base, the basis that is at the core of the idea (product). Creating it – we can immediately get feedback from the client whether he really wants just that or rather wants to take in a different direction.

Very often ideas written on paper and formulated with selected words and evidence seem very logical and brilliant. However, when they are made – it is clear that in practice it is not completely rational.

Perhaps the most striking example is happening at the moment in world history – namely the entry of electric cars. In theory, something incredible and unique, revolutionary and gentle on nature, facilitating movement, comfort, etc.

In reality, however, we see the exact opposite – much more pollution as a result of the production of the batteries themselves, unbuilt charging network, slow car deliveries, expensive insurance, unfinished software in the cars themselves, and many other shortcomings.

The purpose of the scrum is to prevent these situations and, of course, to save all these nerves, resources, documents, and negotiations, by showing the most essential qualities of the desired product from a very early stage and, if there is anything to change, to react quickly. and painless.

Besides, when it comes to an online platform, it is needless to mention that things there are changing day by day. If we start working for months on all the above criteria, when they are completed sometime in the future, half of the functionalities may not be needed at all.

Therefore, it is wiser to focus first on the so-called MVP – the minimum viable product. As I specified above, this is the minimum that the team can deliver in a short time to check the first feedback from the client. In our case, we can reduce all the amazing ideas to a few basics.

The finance department is also usually of the opinion that if we had to deliver all the ideas, it would cost the company a lot of money and time, which does not guarantee any long-term return. That is why they offer a reduction to a minimum that we can all agree on (such decisions are good to make by the Product Owner) and to rank in order of importance.

Here is another reason for joy – employees are already subconsciously beginning to be actively involved in scrum thinking. It would also be good to organize some short training to explain the MVP to the whole team – so that everyone is aware of the principle and meaning of this lesson. I would be happy to conduct this training, and this is exactly what would strengthen the connection between the people in the team and would make them feel part of something common and whole.

But let’s not miss the stakeholders: this must also be agreed with them, and no one refuses a finished product for a few weeks for feedback. We need to be guided by their done criteria and how they define the basics.

When they tell us that it is of paramount importance for them to see the option of advanced property search by multiple parameters, because this is their USP – it makes no sense to waste time developing Android and iOS applications or various login methods. Let’s show them what they most want to see, let them approve it and then we will drink the little details.

When the team sees such a task (specific and with an end date), there will certainly be no element of fright or fear, as would be affected by a sheet of 20 different ideas awaiting development.

In this way, understanding and accepting the MVP as a principle after employees will become natural and on its own, without being imposed on them as something new and annoying.