Skip to content

Instantly share code, notes, and snippets.

@GeeH
Forked from elstamey/user-story-mapping.md
Created January 11, 2016 19:27
Show Gist options
  • Save GeeH/5b32c7b5337b9116c0b5 to your computer and use it in GitHub Desktop.
Save GeeH/5b32c7b5337b9116c0b5 to your computer and use it in GitHub Desktop.
an abstract for a talk I'd like to present

Working in a cluttered work environment is really distracting. We have a lot of potential features to deliver, and we don't completely trust our users to prioritize them. Wanting to help these users we begin to override some decisions. At some point before the project ends, we realize that we implemented a feature based on bad information. As much as we want to blame this on the user, it is not their fault.

Changing the way we talk to our users about their needs, we can avoid some of these pitfalls. We will put more of these decisions and priorities in the hands of the users and set reasonable expectations with them. We will investigate how to drop the idea of minimum viable product and instead deliver the most valuable features first. We will prioritize user stories by the objectives they solve.

Possible titles:

  • Forget the MVP, Deliver the Most Valuable Features! (is MVP widely known enough as Minimum Valuable Product?)

  • Value-Driven Development

Yes, the titles are hard.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment