Learning about user story mapping
User story mapping is a way to put user stories into context, identify what it takes to implement them, and plan accordingly.
In this section, we will learn what a user story is and how it can be used as a planning method, in order to choose what features to include in each release, following a meaningful pace.
The user story is the same concept that we saw as part of BDD. So, it describes a feature from the point of view of a specific persona (As a...), the functionalities required (I want to...), and the expected outcome (So that...).
As you might observe, all pieces in the puzzle of those seemingly unrelated practices eventually start to match. User story mapping is often described as a product backlog on steroids.
We will discuss product backlogs in the next chapter. However, for now, consider them as lists of features to implement. Features are added as long as analysis occurs (or new requirements arise). These are then prioritized...
