Story mapping consists of ordering user stories along two independent dimensions. The “map” arranges user activities along the horizontal axis in rough order of priority (or “the order in which you would describe activities to explain the behaviour of the system”). Down the vertical axis, it represents increasing sophistication of the implementation.

Given a story map so arranged, the first horizontal row represents a “walking skeleton“, a barebones but usable version of the product. Working through successive rows fleshes out the product with additional functionality.

Also Known As

User Story Mapping

Expected Benefits

One intent of this practice is to avoid a failure mode of incremental delivery, where a product could be released composed of features that in principle are of high business value but are unusable because they are functionally dependent on features which are of lower value and were therefore deferred to future releases.

Common Pitfalls


Potential Costs



Signs of Use


Skill Levels


Further Reading

  • Join Agile Alliance and Support Our Mission

  • BYOC Agile Lean Coffee

  • Agile2022 Super Early Bird Registration Discounts

  • Your Agile Alliance Membership Helps Our Mission

  • Game On – Applied Learning with Agile Games

Agile Alliance Resources

Help Us Keep Definitions Updated

Let us know if we need to revise this Glossary Term.