I have a weird, somewhat heretical idea of merging the backlog user stories with documentation. To put it simply, treat the backlog as documentation. Although many challenges arise. The inability to turn everything into a document (or set of documents), the need to control changes so there will be no sabotage in the Team. Yeah, no known to me tools allow to keep that idea afloat ;-)
I cannot agree more. You can use a user story map for an overall view, link to Confluence or Wiki pages for visual details, and Gherkin to break down the story in the description section of the ticket. I also believe they do not need to be user stories. Job stories can be much better for describing game features.
I have a draft of this very subject that will be posted soon!
I have a weird, somewhat heretical idea of merging the backlog user stories with documentation. To put it simply, treat the backlog as documentation. Although many challenges arise. The inability to turn everything into a document (or set of documents), the need to control changes so there will be no sabotage in the Team. Yeah, no known to me tools allow to keep that idea afloat ;-)
I cannot agree more. You can use a user story map for an overall view, link to Confluence or Wiki pages for visual details, and Gherkin to break down the story in the description section of the ticket. I also believe they do not need to be user stories. Job stories can be much better for describing game features.
I have a draft of this very subject that will be posted soon!