Skip to content
This repository has been archived by the owner on Feb 25, 2020. It is now read-only.

Task Assignment

Cyrus Raitava-Kumar edited this page Mar 31, 2019 · 2 revisions

Task Assignment

For the sake of task assignment, the group had long and difficult discussions on what the best approach was. These can be seen in the Team Minutes. These were directly linked to the overall team hierarchy.

Delegation of 'tech' person, + 'spokesperson'

The first idea that was floated, was that the entire group of 25 be split into 5 teams of 5, and each sub-group of 5 have both a person that felt comfortable with the technical domain, and another who would act as a spokesperson for the group, for high-level decisions to be made.

After deliberation, this was decided against, as neither role was found to be too necessary.

Finalised Process

The sub-groups formed were found to still be usable; for those of the team who were keen to pick up large tickets, they could ask if anyone else in their sub-group was also keen, and work on splitting up the task between them. That way, work could be distributed, in a fair and safe manner. We also worked to ensure everyone had equal opportunities at work, by creating a channel in Slack, for notifying each other of open tasks to be done.