YDS: Should a Scrum Team Use Minimally Viable Product (MVP)?

Today's question explores whether or not a Product Owner should the concept of a Minimally Viable Product (MVP) as a tool for agile product development. MVP has a lot of baggage that comes along with it. Todd and Ryan start with defining MVP and break it down from there. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley.

What do you think about MVPs? Let us know in the comments!

This is one of those Scrum Master interview questions about Scrum that can throw you off. Do you understand how easy it is to abuse the MVP concept? These Scrum Master day in the life questions can be tricky. Perhaps some Scrum Master training could help?

Buy Fixing Your Scrum: Practical Solutions to Common Scrum Problems -

Join Ryan and Todd in a Professional Scrum Master course:

And make sure you subscribe to the channel!

DISCLAIMER: Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide, I may receive a small commission. There is no additional charge for you! Thank you for supporting the channel so we can continue to provide you with free content each week!

FTC DISCLAIMER: This video is not sponsored by anyone.

Sharing Scrum knowledge to help you grow as a Scrum Practitioner and to solve complex problems.

#scrum #agile #professional scrum

[g-ronnmendoza]

MVP to some organizations are not about “testing the water”. They really want a “big bang” approach, everything we think should be there.

[amylane]

This is a great discussion. We have no common understanding of what an MVP should be in our organisation, this is really helpful to provide context thank you!

[vkxcqsn]

I hate it when people use the MVP term. It is so overused in ways that it was not intended to be used. Even certain certifications use MVP in the incorrect way. I was fortunate that my CSPO instructor actually used it the way it was intended.

In my previous org, they used the term MVP. My project was the first one to use adhoc Agile there. Fortunately, the System Engineer, on the team, had a commit to excellence and the success of the project and the team. So, he didn’t use the term as an excuse to release a cruddy system. I am not sure if MVP was further Frankensteined after I left though.

[CS-mqgd]

The most anti-definition of MVP I have encountered is "Lets do MVP. MVP = Phase". People coming from waterfall background immediately look for 1-1 mapping and deep root this anti-pattern so much that it is very hard to cut it off at grass roots level in the org.

[jocoign]

I think I have heard 1000 times, let's do this quick and dirty, it's an MVP !
And I feel pain when I know that those words came from product management people PO, PM, BO what so ever was the framework people used...
Now I say, you push for a dirty things ? You won't find someone here that will want to do that, so may be we need to have a serious talk?

[lastphil]

By Eric Ries définition mvp does not always require development or a working software ie. The dropbox example

[MrAkkim]

MVPs are truly often used in the wrong way within organizations that has adopted Agile as their new way of working.