Team

Team Page

Team Members & Roles

The team was broken down into roles in order to increase the project efficiency. Tasks and roles were delegated based on the individual skills and experience of each team member. Specific roles, such as documentation, could have many team members contributing at the one time, whereas others could not; so this was also taken into consideration.

Name	Role
Wesley	Documentation, Project Management
Mathew	Database, Graphics and UX, Frontend
Gareth	Machine Learning, Backend
Neil	Database, Documentation
Hayah	Graphics and UX, Documentation
Nancy	Frontend, Documentation

Each of these roles is further detailed in the Team Roles.

Client

Stakeholders in the project

• TechPot
• Orange
• DNUI

Team Values

1. Trust: Team members must work together in a supportive environment where each person can trust one another.
   
2. Innovation: We encourage outside of the box thinking and support unique and creative ideas.
   
3. Improvement: Everything can be improved, whether it be our ideas or ourselves, we can learn and grow in knowledge, and we can update and advance existing solutions.
4. Passionate: We enjoy what we do and have a desire to produce good solutions to problems. We have fun while working.
5. Focus: All big ideas start with small steps. We mustn't forget to focus on the small details like planning and structure.
6. Efficiency: We prefer to take time writing something efficient then to rush and make something messy that works. Modular solutions that can easily be tested and updated save more time in the long run.
7. Communication: Ideas need to be clearly communicated between team members so that the project can run without being stopped by confusion or small miscommunications.

Team Communication

Problems

1. Team members speak different languages making communication and translation of ideas hard to explain.
2. Team members come form varying backgrounds within tertiary education, resulting in separation between the levels of knowledge of team members. Technical language or complex ideas about a specific field of knowledge are hard to understand for different team members.
3. Working on different tasks at the same time within a project makes communication very important and small miscommunications can lead to big problems.

Solutions

1. Take time to clearly understand what a team member is trying to say. Translation software can be used to directly translate meaning, but sometimes diagrams or pictorial methods of explaining can be just as helpful.
2. Using less technical language and explaining a little bit of background knowledge can help to make these situations easier. Having a good plan and task structure helps to avoid situations where technical explanations are needed.
3. Planning and task management is very important, but time should also be taken every day the project team meets to make sure everyone knows what each part of the team is working on.

References:

1. 8 core values every team should have