Zak Olyarnik | PPJ Week 1: And...Break!

WEEKLY NARRATIVE

Mergers.  I'll admit that I was surprised SPARK wasn't the game chosen to move on, but that won't stop me from whole-heartedly throwing myself into this new project.  Our first team meeting was a discussion about where we envision the game at the end of the quarter, in terms of story, gameplay features, and most importantly, what we know we need to jump on and get fixed right away.  I'll be happy continue to be the Scrum Master this quarter, and it looks like I'll be Code Lead again as well, but I hope to change the description of that position from "does a huge amount of coding" to "organizes the other coders and makes sure that everyone is working on what they want to".  My main task so far has been to create the template for everyone to follow for these PPJs (for team consistency), but I've got a few more things ready that I'm waiting to bring out at our first programmers' meeting tomorrow.

CONTENT WITH HOURS

• Preliminary team meeting (3 hours)
• Creating PPJ format, including troubleshooting with other team members (1.5 hours)

WORKFLOW EXAMPLES

Side-by-side of what the PPJ format looks like in the blogger preview vs. when posted on the team website

POSITIVE OUTCOMES

• So far, it looks like I'm going to be doing exactly what I want on this project.
• Communication has been good for such a large team.

NEGATIVE OUTCOMES

• My work-ethic is very results-oriented, so I hope I'm not coming off bossy when I keep asking teammates for things and checking up on their progress.  This is especially prevalent considering that I'm a new addition to the team.
• Blogger likes to change formatting in its "Preview".  Why do you think it took an hour-and-a-half to get this template locked down?
• Trying to schedule a meeting time, even for a subgroup of the team, is proving to be impossible.

NEXT TASKS

There is a programmers' meeting planned for tomorrow to distribute the first real work on the project, and a management meeting for afterwards to start into the more administrative-type deliverables.

TOTAL HOURS LOGGED THIS WEEK: 4.5 hours

TAGS

#{Zak Olyarnik}

#{Week 1}

#{Documentation}
#{Management}