For your first jam, getting anything accomplished is a feat, even if you have been making games for a while (my first was in QBasic on a Pentium 90MHz, and didn't start jamming until about 5.5 years ago). In the end if you can make something that compiles and is more or less playable, that is good. My first jam team had 6 people. Me, another programmer who merged changes that broke all my code half an hour before the deadline, a person who literally did nothing, a 3d artist who made 3 different small models of asteroids, a 2d artist who made a single 2 frame animation for a 16x16 pixel character, and a writer whose content never made it into the game. So yeah... having anything is good.
Viewing post in Mesolithic jam comments
Team's aren't usually that challenging. That particular game jam was my first and everyone on the team's first. None of us knew the tools (that was all of our first time using Unity and no one had experience with any other engine.) All of my teams since then (6ish years) have been mostly good, and part of that is experience on how to lead a team when they need direction. I love to work with new people and teams as much as possible and usually try to work with someone that is their first game jam. I see a lot of developers in my local area that work with the same teams every time, and that works for them. I like to work in the community to give new people a chance and invite them in and try to see that they have a positive and enjoyable experience. The number one thing is communication, with trying never to be negative about ideas and thoughts. This often means being a bit fluid with the design to accommodate whatever comes up. Next just make sure that if someone makes an asset, try to get in in the game somewhere. If nothing else, flatten it out, put a cube behind it, remove the colliders and call it a poster on a wall. So... I am rambling... but what i am trying to say is teams are very valuable and important to me.