I'm going to be in charge of administration/communications in a small project (16 programmers in total including myself).
We're all fourth year computer engineering majors, and we'll be developing for a certain client using c#/silverlight. We're following a heavyweight Unified Process approach (hw use case driven model), and I need to set the communications framework and the first iteration plans. The problem is I haven't met with the client yet, and I won't meet before I need to hand in this documentation. I'm trying to be as clean and thorough/traceable as possible but I have really no idea what I need to do for the communication framework, so I'm asking what are the most important things regarding this? I figure we must have an 'official', traceable internal communications channel where we can resort in case something is not clear (i.e. dispute over responsibilities, for example I could manage a system where all official communications were CCed to my mail) but after that I really don't know what is expected of this.
I just spend some time googling, and lots of things come afloat: internal/external channels, internal communication hierarchy, etc. How am I supposed to give a meaningful answer to all this questions if we don't even know how we're going to divide the work? The only thing so far we have established are roles: administration/communication (me), software architect, SQA, verification, documentation, UI, SCM, analysts (5), tech specialist (4).
Also, I'm interested to hear from experienced PMs for advice regarding common newbie mistakes, so I can incorporate this to my own experience without having to fail myself.