{"id":5003329,"date":"2015-12-16T23:51:21","date_gmt":"2015-12-17T07:51:21","guid":{"rendered":"https:\/\/aadev22.local\/?post_type=aa_glossary&p=5003329"},"modified":"2023-03-08T16:03:34","modified_gmt":"2023-03-09T00:03:34","slug":"story-mapping","status":"publish","type":"aa_glossary","link":"https:\/\/agilealliance.org\/glossary\/story-mapping\/","title":{"rendered":"Story Mapping"},"content":{"rendered":"
\n
\n

Story mapping consists of ordering user stories<\/a> along two independent dimensions. The \u201cmap\u201d arranges user activities along the horizontal axis roughly in the order in which the user would perform the task. Down the vertical axis, user stories are ordered by priority and\/or increasing sophistication of the implementation.<\/p>\n

Given a story map so arranged, the first horizontal row represents a \u201cwalking skeleton<\/a>\u201c, a barebones but usable version of the product. Working through successive rows fleshes out the product with additional functionality.<\/p>\n<\/div>\n<\/div>\n

Also Known As<\/h2>\n
\n
\n

User Story Mapping<\/p>\n<\/div>\n<\/div>\n

Expected Benefits<\/h2>\n
\n
\n

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 that are of lower value and were therefore deferred to future releases.<\/p>\n<\/div>\n<\/div>\n

Origins<\/h2>\n
\n
\n