<?xml-stylesheet type="text/xsl" href="https://uat.community.rws.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>User Story Mapping Experience Manager</title><link>/product-groups/tridion/tridion-sites/b/blog-posts/posts/story-mapping-and-experience-manager</link><description>My last post described how we can divide a software component such as Experience Manager (XPM) by gathering &amp;quot;Jobs-to-be-Done&amp;quot; into various use cases. 
 This overview lets us then group the XPM Graphene implementation into features, or sets of work that</description><dc:language>en-US</dc:language><generator>Telligent Community 12 Non-Production</generator></channel></rss>