Monday
It’s good that we understand the work of the team members, and drafted a team contract to facilitate our future better cooperation and communication.
In response to the common risks in group cooperation, our team has formulated the following core prevention and response strategies:
1. Attendance and participation
· Prevention: Clarify the rules of regular meetings and absence in the Team Charter, implement the “partner system” to ensure information synchronisation, and make the progress of all tasks transparent through slack.
· Response: In case of absence, synchronise the information in class in time, and the team will give priority to adjusting the division of labour to ensure the progress. At the same time, keep communication records, and report objectively to the tutor in time when the impact is significant.
2. Team communication
Open group meetings every week or use slack for timely communication.
3. Workforce allocation
· Prevention: Disassemble the big goal into small tasks and claim it publicly, use the Kanban tool to visualise the workload, and determine each other’s workload in the weekly regular meeting.
· Response: Encourage role cross-learning in order to make up flexibly when necessary, balance the burden of the team, and help team members complete some tasks when one person’s workload is large.
4. Technical obstacles
· When team members encounter technical obstacles, if they can’t solve it within the specified time, they will ask the team for help to avoid personal obstruction of the overall progress.
Summary: We systematically reduce collaboration risks through front-end rules, transparent processes and focussed communication to ensure that the team can focus its core energy on project development and content creation itself.
Thursday
We have developed a backlog board. First, write down the User stories according to the GDD/vertical slice, and then summarise the solutions and what everyone needs to prepare for these user stories, what they are doing and what has been completed. This is our current backlog：
Each of us received an event schedule next Thursday (2.12), which indicates the content we need to give a speech. Adi suggested that we use Google PPT to display and share our content. We have sent our gmail to him and built a shared document to synchronise the tasks we have completed and unfinished projects. In order to prevent a person from being under too much pressure, everyone speaks at least once during the speech, so as not to focus the pressure on one person, and we will take turns to talk about our own part.
