My team and I are currently creating a 3D tower defense game with Unity and are compromised of me a few animators modelers and programmers. However as I am still fairly new to Unity I have trouble figuring out ways to collaborate with them. I know not what practices or advice I could get on the front of developing this game. I was hoping someone here might have some insight as to how best to collaborate with all team members and what one might do to get a better flow of information and help or assistance when working on this project. We are all about an hour or more away from each other so we must work remotely to collaborate. Thank you in advance.
It depends on many factors so this answer will have to be rather vague. There's also almost nothing Unity specific in your situation.
First off, there are several completely different ways to use Unity, and most of them are equally right. You will have to find a way all teammates agree with.
Regarding tools, source control is mandatory. If you know about source control, chose whatever people on the team are most familiar with. If you don't, use git. It will take the team a few days to get familiar with it, and they will screw up in the beginning, but this is the single most valuable tool you need for collaboration. Make sure you have a central repository where everyone checks in their code at least once a week (if you're doing this professionally full time: once a day), and which should always be working. Use Continuous Integration to make sure it
Beyond that you need regular team calls with a medium of your choice, could be WhatsApp, Skype, some fancy meeting software, or maybe even something totally crazy like landlines (if you can figure out how to do group calls with those). In these meeting the team needs to share what everyone's been working on, and what everyone is going to work on. Make sure people can use the same tool to contact each other whenever they want/need, and also provide a way to have collaborative whiteboard sessions - this can be done with whiteboard plugins on skype, or with teamviewer and paint, or in a million other ways.
Next, to share the vision of the product you may need a Wiki. Diagrams of how screens interact, paper drafts of GUI screens, description of the story, all that stuff goes there.
Last but not least you need to manage a shared todo list. Something like fogbugz, rally, or jira.
Now, for the slightly more Unity specific stuff, the programmers should use mock objects as prefabs, e.g. a cube for a tower, until the designers have the actual object ready, so the designers can simply replace the prefab and everything still works.
All the gritty details of how the people want to share the work, how much of the work should be done by the designers vs the programmers, and how much code the designers should touch depends 100% on your team members, so the team will figure that out during the team calls.