Why MVP Doesn't Mean Deliver Things Quickly
Avoiding small term gain for long term pain
I’ve been in software development for over twenty years now and some things never change.
Stakeholders want things quickly
Development teams want things built properly
Product managers want to make everyone happy.
The challenge is that with the desire to get things out quickly (either to deliver value sooner or find out if the market is keen on what we’re offering) sometimes we cut corners to cut time.
We might then get something out quicker but at what cost?
One of the other things that haven’t changed across my software career is that when you cut corners to get out the “MVP” the chances are that future iterations will also be built on that same “cut-cornered version”.
That’s because future iterations are also wanted in that same prompt manner and there’s a push to get them out sooner too, which means you won’t spend time to right the wrongs of previous releases unless you absolutely have to.
The aim should be to provide building block iterations.
Read on …
Keep reading with a 7-day free trial
Subscribe to Getting Started in Product to keep reading this post and get 7 days of free access to the full post archives.