• Always be aware of scope, think small then cut it in half. K.I.S.S.

• Choose an engine or framework you are already very familiar with or partner with someone who does

• 3D takes 4 times longer than 2D, choose wisely

• Choose the path of least resistance (ie. don’t get stuck on anything!)

• Don’t be afraid to fail and show your failure. We can all learn something from failure.

General Guidelines

• - Too much or too little brainstorming!

• - Making the concept or feature set too big. You don’t have all the time in the world!

• - Programming problems. Stuck on some programming bug? Don’t try to solve it, work around it.

• - Forgetting about sound and music. It makes a difference.

• - If in a team, don’t fight! Its all about fun and learning at the end of the day.

• - Hoarding or secrecy. In a team, share your code, art, music, writing, drawing and especially ideas. Ideas are worthless without a team to implement them.

• - Lack of food or sleep!

• - After getting the theme or constraints, brainstorm! Write all ideas down.

• - Prototype your ideas (physical/paper ones if possible). Find out which can be done in the time allotted.

• - Pander to your best skills and those on your team (for example, if you're an artist, make the art style a big part of your game)

• - Once settled on an idea, reduce it to its smallest component/mechanic and build around that.

• - Test Test TEST!

• - Cut features or ideas if taking too long or detours too far