This last week I worked on three user stories during the sprint:
- Create a task list of handling combat between PC and NPC.
- Using that task list, write the combat code.
- Create a progress report for the project.
The first user story was created at the suggestion of Dr Banks since I was having a hard time figuring out where to start in doing the combat. That worked — about halfway through the task list it kind of gelled on how to handle coding the combat module.
The second user story, actually writing the combat code, didn’t get finished. While the core of the code did, the audio and visual effects that go with the fighting weren’t in, so that user story went into the backlog (and is being included in the first of two sprints this week).
The third user story was finished by setting a “percentage done” for each of the main parts of the “When the Game is Done” document (last page of the design doc).
Thinking Ahead Questions
- Discovering the deadline for the game is a week earlier than I thought makes me wonder what I’m going to need to neglect over the next month to get it (and everything else) done. Could be that all I need to neglect is Netflix…
- There appears to be a bug in the animation events of Unity that’s causing the guy to freeze during combat (not good). Wondering whether I’ll have to code a work-around or if a Unity patch will appear before that has to happen.
- Will moving to two shorter sprints per week make a difference in how much I get done? (I think the answer will be yes.)
Time Spent This Week
Total time working on the user stories, including coding the combat routines was about 16 hours and another 2 hours of misc stuff (class, research, reading) for a total of about 18 hours spent on the project this week.
Weekly Total: 18 hours.
Project Total: 109 hours.