This last week I worked on only one user story:
I need to keep track of the inventory items that are picked up in the dungeon.
That was completed with the addition of a new Inventory.cs module that keeps track of gold collected as well as spell books collected and used. I’m also treating health as an inventory item, so those parts are also in the file.
That user story could have been split into two — keeping track of the inventory items “under the hood” and also displaying the current status of each. Those parts are both done and the screen now shows Health, Spell books collected, and gold collected.
Although I only worked on that one thing, it was needed to kind of clean things up that I’d done the last week.
(Note: The bug that I saw in class couldn’t be duplicated afterward, so I posted the user story as done. If it was really a bug I’m sure I’ll run into it again.)
Thinking Ahead Questions
- I’m going to reuse #1 from last week because it’s kind of overwhelming — combat. But the first user story I wrote for this week was to create a task list of combat needs. Break it into parts to know exactly what’s needed.
- Is the game going to be any fun? I probably should have created a prototype of just the “fighting by making words” thing before diving into the whole game.
- I’d expected to send a sample to Mike and Mark, the “stakeholders” by now, but not sure if that’s a good idea since much of the actual playability isn’t even in place.
Time Spent This Week
Total time working on coding the inventory (backend and UI) routines was about 10 hours and another 3 hours of misc stuff (class, research, reading) for a total of about 13 hours spent on the project this week.
Weekly Total: 13 hours.
Project Total: 91 hours.