I think the key thing is to identify the "freeloaders" early.
I was once in a group for a university project when we had to implement this piece of software for a real world client. There was software that needed to be built, and documentation that needed to be written, as well as content that needed to be provided, e.g. weekly meeting diaries one is required to do in such university projects. Everyone else in the group had difficulty writing working, useful code, and progress was slow, even when I thought it was an easy project. A few days before the first milestone deadline, I sat down and finished the thing in an afternoon. And so, for the rest of the semester in that class all we had to do was the paperwork, and naturally that wasn't my job because I saved everyone so much time.
Sometimes BS needs to be written...that's when it's useful to have people who's best to do that kind of thing in your group.
I was once in a group for a university project when we had to implement this piece of software for a real world client. There was software that needed to be built, and documentation that needed to be written, as well as content that needed to be provided, e.g. weekly meeting diaries one is required to do in such university projects. Everyone else in the group had difficulty writing working, useful code, and progress was slow, even when I thought it was an easy project. A few days before the first milestone deadline, I sat down and finished the thing in an afternoon. And so, for the rest of the semester in that class all we had to do was the paperwork, and naturally that wasn't my job because I saved everyone so much time.
Sometimes BS needs to be written...that's when it's useful to have people who's best to do that kind of thing in your group.