In case this gives you ideas/inspiration for your own process of designing your TW use cases:
1 Like
It may be possible to generalise this to game score keeping, one that comes to mind in card games like 500 with a little reference to show points relating to the different suits etc… One could make it in a selection table to just click to set number of tricks and the suit involved. One could even to it to record a bid, then click to indicate the tricks won, when the hand follows.
Of course unless you play you may not understand the above.
The project is called “Game Night Score Keeper”. I thought the title subtly indicates that it is a general score-keeping TW for games.
Maybe my title is too subtle?
I’m not sure what you are suggesting that isn’t in my TW already. For example:
Regardless, the whole point of the post, which maybe I did not make clear in the title, was to offer up an example of putting together a “vision” document to focus the mind as one builds whatever TW use case.