How do you decide on an MVP?

Aaron -

I disagree that the team wouldn't have input into the content of an MVP. For example, the PO might have no clue about dependencies between work items which the team would be aware of.

I do agree that the final decision on what makes it into the MVP rests with the PO.

Kiron

The team doesn't decide the MVP or the duration.

Assuming Scrum, the Product Owner is responsible for defining the MVP (or MBI), but doesn't do it in a silo. An understanding of the product users is needed, which often comes from outside the team.

The team is responsible for sizing the work. The number of sprints needed to deliver the the MVP is the sum of story points in the release divided team velocity. The duration for the MVP then depends upon the length of the sprints, or:

D = Ln
n = ?S_p/v

Where:
D = duration, or time (estimated) needed to deliver the MVP
L = length of sprints; number of weeks
n = number of sprints (estimated) needed to release the MVP
S = stories in the MVP
p = points for each story
v = velocity, or number of points that can be completed per sprint

The only thing the team decides is the estimate for the size of the stories.

Developing an MVP is not an us vs. them situation. There needs to be an analysis of both market questions to be answered and technical approaches and capabilities constraints to answering the questions. The team consists of all parties working together bring their own sets of knowledge and experience. It is not 'I do this, you do that,'