WEEKLY NARRATIVE
A new term, a new game, and a (mostly) new team. I liked both of the games that were the options for this class, and to be frank, liked both of them based on what I played of them from the previous term. Though I knew some of the people in the class, most people were new to me, and I spent a decent amount of time talking to the others in the group.Part of this was staying after the first class and going to the preliminary team meeting, where I also got more familiar to the game and how this team will work. From talking to the others, and seeing how things are handled, along with the hierarchy and leaders in the group, I am sure that though this term will be a lot of work, it will be with good people.
CONTENT WITH HOURS
- Preliminary team meeting (3 hours)
- Play-testing the game and making notes of various bugs (1 hour)
WORKFLOW EXAMPLES
Not much to show here this week. I did not fully use the workflow as shown in the GDD yet, as the only work I did involving this was noting the bugs I found and possible improvements, which I simply made note of on my phone and discussed it during the meeting.
POSITIVE OUTCOMES
- Got to know most members of the group.
- Questions get answered in a timely fashion.
- Meetings are well organized.
NEGATIVE OUTCOMES
- I was not able to attend the story meeting.
- I have not taken too close a look at the code yet.
- There is a programming meeting tomorrow I might not be able to attend.
NEXT TASKS
Try to attend the programming meeting tomorrow and get tasks for the next week, as well as familiarize myself with the code base.TOTAL HOURS LOGGED THIS WEEK: 4 hours
TAGS
#{Trung Tin Pham}
#{Week 1}
#{PPJ}
No comments:
Post a Comment