User Story Mapping ‐ Iteration 1 - NeslihanO/IoT-project GitHub Wiki

User Story Mapping

User Story Mapping is a method for software development. The idea is to develop the product along the customer's journey. This method helps the whole team to get a better and common understanding of the process and product. It also helps to avoid the risk to develop a product that is not valuable for the user.
We used the Story Mapping for our idea. In the first step we created a users story (yellow cards). In the second step, we thought about the user stories to implement along the story.

mvp_1

Definition MVP

There are several definitons of a MVP (Minimum Viable Product). Ash Maurya defines a MVP like: "The smallest thing you can build that delivers customer value (and as a bonus captures some of that value back i.e. gets you paid)."

Eric Ries defines a MVP as follows: "A Minimum Viable Product is that version of a new product which allows a team to collect the maximum amount of validated learning about customers with the least effort."

We consider both descriptions and define our MVP like Ash Maurya says “the smallest thing you can build that lets you quickly make it around the build/measure/learn loop”.

MVP Iteration 1

After creating the User Story Map, we did a slicing and defined the minimum set of functions for our MVP. For this, we defined the minimum amount of functions that deliver value to the user which is a personalized coffee in a faster way. Personalized coffee requires an identification of the user. To enable the identification we require the following functions:

  • Login in Brewbot Portal
  • Creating personalized coffee profile
  • Downloading personalized QR-Code
  • Standby screen on the display of the smart device
  • Authentication via QR-Code
  • Message of brewing coffee
  • Goodbye message on the display of the smart device

With these functions we can realize the identification of the user and a mapping to his profile. Therefore these functions flow to our first MVP.

In implementing these functions we deliver a personalized experience for the user. He gets his personalized coffee faster and in a more comfortable way. He does not have to select his coffee manually or use an app anymore and also saves time.

We did not consider some functions for the MVP because they can be implemented in further iterations and are not essential functions for creating value for the user. For example, these functions include the status of the coffee machine which would give information about the status of coffee beans, water and how much traffic there actually is. In further releases we plan to implement a help desk, a video with FAQ, and a chatbot which answers frequently asked questions. Moreover, we plan to build a coffee community in which users can exchange coffee experiences and knowledge.

Sources: Ash Maurya - Running Lean, Eric Ries - The Lean Startup, Jeff Patton - User Story Mapping