• often use in the beginning of new projects or products. The story map is an excellent way to create a nice overview of all the features you and your stakeholders can think of
  • nice starting point to facilitate creative ideas
  • provides an overview of all the user activities that need to be covered by the system, which in turn enables you to create small and valuable user stories
  • starts with the user activities, and thus taking a users' perspective on the product
  • The main downside is that it creates the illusion that all the features for the product will be developed
  • make it very explicit to stakeholders that you will not necessarily develop all of the stuff in your story map. So manage these expectations well
  • (User Personas), User Activities, User Tasks, Features per UA-UT-Release (can include dependencies)

    • Template

      <aside> <img src="/icons/info-alternate_blue.svg" alt="/icons/info-alternate_blue.svg" width="40px" /> As a (who wants to accomplish something - PERSONA-WHO - User Personas) I want to (what they want to accomplish - OUTCOME - General features - User Activities) So that (why they want to accomplish that thing - GOAL - User Tasks)

      • (Extras) </aside>

    • 5 Key Components

      • User Stories Must Always Have a User! The first point might sound obvious. ...
      • User stories capture what the user wants to achieve in a simple sentence. ...
      • User stories contain a qualifying value statement. ...
      • User stories contain acceptance criteria. ...
      • User stories are small and simple.

    • 3 elements: the 3 C´s

      • Card
        • the ideas are written on the back of the card
      • Conversation
        • a future conversation. It allows you to not stress about the details right away and instead quickly jot something down as a placeholder for a future conversation, at which point you will fill in the details.
      • Confirmation
        • Details of the story or conversation. Rather than endlessly repeating the same conversations, agile teams capture details of a user story just in time. This detail is typically captured as acceptance criteria before a team takes on the story