What you're about to read is a presentation of a slightly unusual way of driving the most learning and the best product out of a group project - my experience is based on mostly big group university projects and my Master's Thesis project, but that doesn't discount the qualities of the approach I am about to present to you.
The elevator pitch of me: I'm a digital designer that changed his path and became a programmer. I am curiously inclined, and a good observer however I am not a talented person. As a matter of fact I am disorganized, conforming and more lazy than I like to be. The redeeming trait I have is that I was raised to be dutiful and this has given me an edge that puts me above the mean - but I'm not a 10x developer nor a 10x student - I'm just above average. But I am curious and good at observing and reflecting!
And accurately enough during most of my university courses I would perform right about average getting right about average grades.
But here and there you would find top grades. And all of these grades had one thing in common: They were all grades based on group projects. But not just any group, a group wherein the culture was just right to