|
|
Stories
I started creating the stories for the server. Having never done this before, I'm basically brainstorming one liners. Things like:
User should be able to choose graphics (board wood, stones, incl. size and color)
User should be able to view "most recent move"
The system should validate the move, reversing it if inappropriate.
The system should be available to score a board but only when game is over
Only allow user to play a single stone per turn.
System automatically removes captured stones.
Note how some say "should" and some don't. I'm not sure how to word them most effectively. I'm not sure how long they should be, how much they should say, how much design and detail they should include.
I'm not sure how to store them. I think we'll keep stories for a release in a text file, plus one file for all unsorted stories. Then, maybe a folder for each release, with a file for each story and its tasks. And then a file for each iteration in the release as well...
That seems overly difficult. What we really need is a web front end for a story-management system... Well. We'll stick with the simplest thing for now. Maybe that can be Scrum's second project.
Meanwhile, I've thought up 49 of them. I'm going back to the XP books to see whether I've got the right idea or not.
|
|
|
|
Post a Comment
<< Home