Our team structure features five roles, as described below, as we believe these allow for timely implementation of the various project tasks (see Gant chart). As we are a smaller team of five members and started of with similar expertise, we decided to assign task responsibility - yet ensure that everyone is informed and when possible, consulted, of the progress made. This is reflected in our RACI chart (see below).
Reason for assignment: With a passion for converting the requirements into visual designs, Yuqing also puts great importance into implementing the user-friendly accessibility option.
**Johanna - End user liasion**
Reason for assignment: With a passion for ensuring that the user's needs and wishes are captured and prioritised, Johanna consults with the User Interface Designer to ensure that these are successfully implemented.
**Meishan - Risk Officer**
Reason for assignment: Meishan is excellent at identifying and mitigating risks related to this development, with her role including that of a quality assurer, a change office, risk officer and test client.
**Redon - Developer**
Reason for assignment: Redon has a past experience for turning the designs into reality and writing clean code, whilst considering the software architecture in place.
**John James - Project manager**
Reason for assignment: John James has an eye for details and has a passion for motivation team members whilst ensuring the Gantt chart and further plans are carried out within the devised time.
**Communication processes**
We believe that effective communication is best achieved through face-to-face discussions. For this we have scheduled (short) daily meetings, when this is possible. We also use a slack group for sharing resources and assisting each other. Editing this wiki is used for version control and enabling us to work on the same document, at the same time.
As the RACI chart shows, the five roles have been made accountable for the tasks within their domain, but task responsibility has been assigned even beyond roles. For example, all roles have decided to take part in designing the user questionnaire, and having a face-to-face discussion with the client, as well as designing the project architecture. We appreciate the opportunity to learn how to use new technologies and methods, and also find it very important to consult each other with regards to more difficult tasks.
