After being instructed that we should have our communications archived and in a more public domain, I will be working over the next week to transfer our communications from the facebook group to a new tab on this web page.
I will create a new blog post for each week's communications up to and including the current week, and will be encouraging the other members to post any updates they have on this new page.
Showing posts with label group info. Show all posts
Showing posts with label group info. Show all posts
Sunday, November 24, 2013
Sunday, October 27, 2013
New Group Policies
Due to last weeks chaotic submission process and deadlines not being met, we have come up with the new policies below.
New Submission Policy: We now have a Deliverables spreadsheet on Google Drive, which can be found here. Each week, your deliverables should correlate with the Gantt chart (also on Google Drive). Send your assets to whoever is listed in the "Submit To" column, by the date and time in the "Submit Time" column. The receiver should then provide feedback to the submitter, and let them know if revisions need to be made. After the asset is deemed finished, the receiver needs to sign off on the spreadsheet, and graded on a scale from 1-5, (1 is bad, 3 is average, 5 is great). This grade will not affect your Diefenbucks unless the quality is a 1 or 2.
Deadlines: All art assets should be sent to Dylan by Tuesday morning. If they're not in, you'll receive a 30% reduction in your Diefenbucks for that week. If they're still not in 24 hours later (Wednesday morning), you'll receive no Diefenbucks for that week. Note: If people abuse the 30% reduction, we'll up it to 50%.
Diefenbucks Distribution: The Diefenbucks we receive each week will be distributed evenly among the group, provided there were no penalties for an individual. If there are penalties, the Diefenbucks they forfeited will be evenly distributed to the other members of the group. For example: we have 8 members in our group. In one week, we earn 8/10 bucks. If every person does their work without any deadline penalties, each person receives 1 buck. However, if Evan was late on his submissions within 24 hours, he will receive 0.7 bucks and the rest of the group will get 1.04. If he's 24 hours or more late, he will receive no bucks, and everyone else will receive 1.14 bucks.
New Submission Policy: We now have a Deliverables spreadsheet on Google Drive, which can be found here. Each week, your deliverables should correlate with the Gantt chart (also on Google Drive). Send your assets to whoever is listed in the "Submit To" column, by the date and time in the "Submit Time" column. The receiver should then provide feedback to the submitter, and let them know if revisions need to be made. After the asset is deemed finished, the receiver needs to sign off on the spreadsheet, and graded on a scale from 1-5, (1 is bad, 3 is average, 5 is great). This grade will not affect your Diefenbucks unless the quality is a 1 or 2.
Deadlines: All art assets should be sent to Dylan by Tuesday morning. If they're not in, you'll receive a 30% reduction in your Diefenbucks for that week. If they're still not in 24 hours later (Wednesday morning), you'll receive no Diefenbucks for that week. Note: If people abuse the 30% reduction, we'll up it to 50%.
Diefenbucks Distribution: The Diefenbucks we receive each week will be distributed evenly among the group, provided there were no penalties for an individual. If there are penalties, the Diefenbucks they forfeited will be evenly distributed to the other members of the group. For example: we have 8 members in our group. In one week, we earn 8/10 bucks. If every person does their work without any deadline penalties, each person receives 1 buck. However, if Evan was late on his submissions within 24 hours, he will receive 0.7 bucks and the rest of the group will get 1.04. If he's 24 hours or more late, he will receive no bucks, and everyone else will receive 1.14 bucks.
Thursday, October 17, 2013
Oct 17 Class Meeting
Today Cory presented our Week 4 scrum presentation which can be found here.
Our presentation overall was good, and we got a few tips on how to improve it. I took some notes.
Our presentation overall was good, and we got a few tips on how to improve it. I took some notes.
- Compare what we said we'd do vs what we accomplished (relate it to the previous week)
- How successful were we, self reflection
- Art
- Show concept art vs prev week vs current
- Art asset checklist overview (show overview, table)
- Gun concept as player would see (player perspective)
- World assets need to fit the theme better
- Programming
- Basic ideas of scripts that were made that week, what they're based on
- "For Next Week" section
- Organize by category
- Programming, art, audio,
- As a whole section
We also had some discussions about our game and debugging menu.What we have so far is a great start, but we need some debug options for the enemy, including speed. For our debug version, we should also show the player's HP.
Lastly, we also really need to hash out our monster, and what makes it scary. It's possible we'll have to do some redesigning of it if players don't find it scary.
Next week we'll have our first playtesters play through our prototype level and give us basic feedback.
Subscribe to:
Posts (Atom)