My last post described how we can divide a software component such as Experience Manager (XPM) by gathering "Jobs-to-be-Done" into various use cases.
This overview lets us then group the XPM Graphene implementation into features, or sets of work that can fit our program increments (a set of sprints aligned across feature teams).
At the start, I was tempted to organize and prioritize the XPM user stories by relationships…
Translate



