WEEKLY NARRATIVE
This week, we held our meeting on Thursday to try and expedite the rest of the work's week and not have to be working so late on Sunday. Well, it almost worked. We were able to get our first attempt at a build out on Saturday night, which gave us a good 24 hours to QA and test. Only the list of problems just kept getting longer the more time we spent looking, and it all culminated at about 10pm with realizing that no one had actually implemented the new enemy's model. I'm just glad we have guys dedicated enough to keep working through the night whenever stuff like this comes up.
Meanwhile, I spent some time this week redoing the sell presentation based on the critique in class, since it's still fresh in my mind. The team decided to go the route of making two presentations, one with improvements based on the feedback, and one pretty much the same as the one we gave, to be delivered at the final for Prof. Diefenbach. That way, we're completely covered, and most of the material is the same anyway, it's just a matter of presentation order. I also went through and changed up the playtest survey, using our data collected so far to remove unhelpful questions, turn short answers into other question types (to encourage more responses), and to ask new questions based on the new levels. We've finally got a good amount of content in our game, so this week's testing is going to be really valuable.
CONTENT WITH HOURS
- Team meeting (2 hours)
- Redoing the sell presentation (2 hours)
- Changes to the playtest survey (1 hour)
- Scrum presentation (2 hours)
WORKFLOW EXAMPLES
POSITIVE OUTCOMES
- The game is really coming together.
- The expedited production schedule this week worked, sort of.
- Plenty of QA testing means that I can feel confident about the build we turn in.
NEGATIVE OUTCOMES
- People still seem to be dropping out of contact an awful lot, but the closer we get to the end, the more important it is for everyone to be on-call.
No comments:
Post a Comment