Replace "user story" with a better term
Closed this issue · 2 comments
We are using "user story" throughout the playbook but I think that adds confusion as we don't in fact use it in a way that most people use it (I guess one could argue we're using it incorrectly even). I suggest we use something that doesn't have any formal definition like "feature concept". In the end what we mean is a bit of text plus diagram(s) that give a good idea of how a feature works conceptually. These diagrams should be something along the lines of what's described in Shape Up as "Breadboarding" plus, if necessary at all, a coarse diagram illustrating some important UI concepts (as referred to in Shape Up as "Fat marker sketches"). The latter should be necessary only when the UI concept is at the core of the feature (e.g. when trying to improve a UI glitch users were struggling with as described in their example).