Group Project Split
Fill this in at the first meeting. The row that matters most is the one naming who owns integration.
BFCBrilliance · bfcbrilliance.com/tools/group-project-workload-splitter
The project
- Module
- Deliverable
- Deadline
- Total hours estimated
- People in the group
- Shared work (%)
- HOURS PER PERSON
- WHO OWNS INTEGRATION
Who does what, and by when
| Person | Section | Hours | Due to the group by | Done? |
|---|---|---|---|---|
The shared work — give every row an owner
| Shared task | Owner | Hours | When |
|---|---|---|---|
The arithmetic, and what does not divide
- With contingency
- total × (1 + contingency%)
- Your section
- divisible work ÷ people
- Your shared share
- shared work ÷ people
- Meeting cost
- hours × people (person-hours)
- A 1-hour meeting, 6 people
- 6 person-hours
- ⚠ Shared work
- does NOT shrink with group size
- ⚠ Coordination over ~⅓
- organising more than producing
At the first meeting
- Total hours estimated before splitting anything
- Shared work listed explicitly, not assumed
- INTEGRATION given a named owner
- Formatting and the reference list given an owner
- Internal deadline set BEFORE the real deadline
- Contingency agreed and written down
- File format and citation style agreed at the start
- Agreed what happens if someone misses an internal deadline
Integration is the task that belongs to nobody
Merging four sections into one document with one voice, one format and one reference list is real work. If it has no owner at the first meeting, it lands on one person in the final week — and that is the week with no slack left.