I have a book that I'm rewriting right now, that relates to game design and team management. Since I'm rewriting it, I'd like to get more outside opinion this time. I have a section on Roles and Tasks. It is intended for a free lance team to review:
1) To see the common roles (Game Designer, Level Designer, Graphic Designer, Programmer, Administrator, DBA, Mathametician, etc...), and compare what there team has, and what tasks are commonly associated with those roles. I.e. if someone comes into the group and takes on the role of Marketing or Programming, it lists what they and their team should expect from them, and give them the change to include or subtract things as needed to keep everyone on the same page about their responsibilities.
2) For roles that the team doesn't have covered (which a single person can be multiple roles), they can see the types of tasks they would be expected to do, and make sure they look what they need covered. I.e. a lot of indie teams don't have any one on marketing, and so will push off all marketing until the last possible time to work on it, when marketing should help shape the GDD in most cases (making sure they are targeting salable features for instance, instead of white noise.)
Anyway, my question to you is to name a role in a game development team and what responsibilities that might include. (Its normal for different places to assign different titles to a person with the same set of tasks, or the same title despite having different common tasks) I'm just looking for what your experience has showed you.