Communication

This would be great, because I have no tasks at the moment.

Communication Meeting results


What happens when groups don’t communicate?

Clearly defining the goals
- Going off on tangents
- you can’t properly iterate on your own idea
- Inability to solve the problem
- Underestimating time budget
Who is defining the goals?
Do not outcast members
- Members feeling distant might not feel capable of being a part of the group
It’s easy to assume that other members are not doing as much work as you


Team Complaints/Issues
Vision carrier Vs. Production Lead – define these roles
Low cash budget for some team members
- limits transport to attend physical meetings


Things to Change
Relieving the bottleneck problem
Communication
- 3 times per week – Manager will organise this
- share some of the management to others
At least one face to face as a Scrum Meeting
Includes Skype calls
- Meeting minutes – Cam
- Forum – Cam
- Email around – Including Josh – Phil
- Notification of absence – Phil
Make sure everyone knows what they’re doing
Sprint Goal
- Clear to everybody
- Tasks reflect this

Peer Review
- Everyone should be doing this and shouldn’t bottleneck through anyone
- Build Review – end of sprint (locked in time)
- Buddy System – A task is not done until it has been reviewed – any member can do this - The team members in general are always on Facebook – Cam should contact directly for things
- Tasks:
- Time Estimate
- Reviewer

- Taking a step back and teaching others how to solve the problem opposed to tackling everything by themselves

Shift thinking from being students to how you would work as a company
what do you do when you’re trying to earn income with the project

Tools to support production
Download Play Maker
- from the Unity Asset Store
- node based system like UDK
Workshop
Training in Unity Programming


Passing around support
Documentation – Oggie and Phil
Art – Ash will support with 2D
Unity – Cam will shift documentation to others so he can focus on Coding


Meeting Plan
Regular
Thursdays – Pure meeting session
Three Extras
Saturday – Skype Call – 3pm
Monday – at 5pm at Qantm

Scrummy – It feels very out of the way
- A new way to document our scrum process might be needed


Consider how will the timetable change during next trimester?

Josh and the team must be emailed about absences before Tute Sessions. CC or re-email all messages about absences to Josh a day before the session.

Josh’s Email: j.birse@sae.edu

If a team member is late to Mandatory Sessions, they must contact Josh as well as the team. Missing team members will be messaged during their absence.
If Cam isn’t at a meeting to contact team members, please text message him.
The risks from team members not showing up create serious red flags. If absences are too ambiguous to Josh, he may send out warnings. The number one reason why a team must be pulled apart is for poor communication.
There were too many scenarios where needed work isn’t provided and isn’t reviewed.


New Schedule
Monday = Mandatory Session + Week Start
Tuesday = Mandatory Session
Wednesday/Thursday = Midweek
Friday = End Week Meeting at Qantm