Team Members:

• Alisa Castillo
• Camille Clerc
• Ganaka Wijesundara

• Programmer:
  • Head: Ganaka Wijesundara
  • Backup: Camille Clerc
• Builder:
  • Head: Ganaka Wijesundara
  • Backup: Alisa Castillo
• CAD:
  • Head: Camille Clerc
  • Backup: Alisa Castillo
• Presentation:
  • Head: Alisa Castillo
  • Backup: Camille Clerc

Ganaka Wijesundara: Will be lead programmer, builder, facilitate productive discussion/ brainstorming, and deadlines. I will edit Gantt charts depending on scheduling conflicts, assign small programming tasks to Camille and building tasks to Alisa.

Camille Clerc: Look over the team and makes sure everyone is on task in order to follow our agenda, and makes sure that we are conducting work in a positive and productive manner. Leads CAD projects and supports presentation and programming activities within the group. I will break down CAD tasks to Alisa and ask Ganaka for input. I will also support and aid Alisa in presentation and Ganaka with programming activities.

Alisa Castillo: Will be lead member responsible for the presentations and written documents that pertain to the assignments on hand. In addition, be a back-up builder and CAD aid when needed and possible. I will assign tasks/ask for help and input from Camille when creating presentations.

Everyone: As members of a team we will be flexible, when needed, in order to adhere to team assignments/work. We will make each other aware of any changes to our schedules and if individual assignments may not be able to be completed by a group assigned due date. Conflicts will be dealt with with maturity and respect, allowing both sides to voice their opinions, and working against the problem, not the other members. Conflicts will be dealt with by participation of all members, and as quickly as the problem arises.

Scheduling: The leader that will delegate, schedule, and help resolve group contracts will be Ganaka Wijesundara.

Previous Experiences:

Ganaka Wijesundara:

I have been in IED, POE, Afterschool/middle school robotics, and SkillsUSA. I also have certifications in Microsoft Word/ Powerpoint, Inventor, Fusion 360, block based programming, as well as experience in javascript, java, html, python, and css.

Camille Clerc:

Took IED course and learned how to use CAD programs. Through this course, I earned an Autodesk Inventor User Certificate. I also have experience in block based programming, javascript, and python. I’ve also been in after school robotics and SkillsUSA.

Alisa Castillo: I was in IED last year and learned how to use Inventor. Furthermore, I made a website for Mr. Hicks’s eighth grade Biology Course which was a long-term project. I am an Autodesk Inventor Certified User. In addition, I am certified in Microsoft Office Specialist Word 2016 and Microsoft Office Specialist PowerPoint 2016. Over the summer I familiarized myself with Python and during this school year I got to learn more about Raspberry Pis and its functions.

Group Names / Contact Information

Includes the names and contact information of the people in the group

Name: Alisa Castillo

Email Address: Taken Out Due to Privacy

Phone Number: Taken Out Due to Privacy

Name: Ganaka Wijesundara

Email Address: Taken Out Due to Privacy

Phone Number: Taken Out Due to Privacy

Name: Camille Clerc

Email Address: Taken Out Due to Privacy

Phone Number: Taken Out Due to Privacy

Group Goals

• When conflict arises, we will be respectful, we will speak to ideas, not people, and we will try our best to use these disagreements to further develop our ideas.
• We will work together to accomplish our individual and group assignments in order to complete the main project successfully.
• We will aim to turn in quality assignments.
• We will strive to be punctual and flexible with our schedules.
• We will brainstorm together with an open-mind and offer constructive criticism towards our member’s ideas.
• We will practice active listening and nonthreatening confrontation.

Group Members Responsibilities

• Programmer:
  • Head: Ganaka Wijesundara
  • Backup: Camille Clerc
• Builder:
  • Head: Ganaka Wijesundara
  • Backup: Alisa Castillo
• CAD:
  • Head: Camille Clerc
  • Backup: Alisa Castillo
• Presentation:
  • Head: Alisa Castillo
  • Backup: Camille Clerc

Ganaka Wijesundara: Will be lead programmer, builder, facilitate productive discussion/ brainstorming, and deadlines.

Camille Clerc: Look over the team and makes sure everyone is on task in order to follow our agenda, and makes sure that we are conducting work in a positive and productive manner. Leads CAD projects and supports presentation and programming activities within the group.

Alisa Castillo: Will be lead member responsible for the presentations and written documents that pertain to the assignments on hand. In addition, be a back-up builder and CAD aid when needed and possible.

Scheduling/ Class time:

• Time constraints: Everyone can meet on Fridays afterschool (Potentially Wednesday). Weekends fluctuate, but if needed everyone agrees to move their schedule around to abide by team meetings.
• We we will do our best to be productive with the time given to us in class and try to advance our projects some way every time. (Turning over rocks and finding nothing is progress).
• It is up to the individual to manage their own time on their individual tasks, but the task manager will make sure everyone is on task.

Listening/ Conflict Resolution:

• We will be open-minded to the other members.
• When brainstorming each member must listen to the ideas to others and not disregard it right away, brainstorming is meant to get every idea out.
• We will manage and resolve conflicts through the use of open and calm conversation. Clear communication on what the problem is and productive debates are the only ways of successfully working through conflicts.
• Conflicts will be dealt with with maturity and respect, allowing both sides to voice their opinions, and working against the problem, not the other members. They will be dealt with by participation of all members, and as quickly as the problem arises.

Confidentiality:

• The information written within our Engineering Notebooks will be honest and will show integrity.
• We will not falsify information, and clear signatures on each page will hold witness.

Decision-Making

• We will use Gantt/ Matrix charts to facilitate our decisions on making different ideas that may conflict among the members in the team.
• Will be realistic when choosing our goals and group deadlines as there will be many cases where we will have to adjust these as problems arise.

Steps for censuring group members

Describes the warnings and disciplinary actions that the group can take (including appropriate steps to being fired from a group)

• Missing group deadlines will lead to warnings and disciplinary actions:
• 1 missed assignment will lead to one warning.
• Outright disagreement and noncompliance with the team leads to one warning.
• 3 warnings will lead to a meeting with Mr. Hicks seeking council on actions we should take with the problem.
• One more incident of any listed above after the meeting with Mr. Hicks will lead to being fired from the team.
• Everyone will have a page in their Engineering Notebook dedicated to recording the number of warnings/incidents.

Accountability

How you will hold team members accountable to their performance on the task or project

• We will complete our individual tasks on time, in a manner which is not a hindrance to other team members and give notice at least 3 days in advance if problems arise, the task cannot be completed, or deadline cannot be met
• We will contact each other outside of class at least once a week to make sure deadlines can be met and any problems risen can be solved
• If the task cannot be completed due to an unpreventable emergency and 3 days notice could not be provided the task will fall upon the backup. If the reason is valid, then a warning will be excused.

Acknowledgement

A place for each team members signature as a sign of their understanding and commitment to the team.

• Ganaka Wijesundara
• Camille Clerc
• Alisa Castillo

Our Team Norms (Notes)

Example of Team Norms PDF Link

Time

1. Time constraints: Everyone can meet on Fridays afterschool (Potentially Wednesday). Weekends fluctuate, but if needed everyone agrees to move their schedule around to abide by team meetings.
2. We we will do our best to be productive with the time given to us in class and try to advance our projects some way every time. (Turning over rocks and finding nothing is progress).
3. It is up to the individual to manage their own time on their individual tasks

Listening

1. We will be open-minded to the other members.
2. When brainstorming each member must listen to the ideas to others and not disregard it right away, brainstorming is meant to get every idea out.
3. We will manage and resolve conflicts through the use of open and calm conversation. Clear communication on what the problem is and productive debates are the only ways of successfully working through conflicts. Conflicts will be dealt with with maturity and respect, allowing both sides to voice their opinions, and working against the problem, not the other members. They will be dealt with by participation of all members, and as quickly as the problem arises.

Confidentiality

1. The information written within our Engineering Notebooks will be honest and will show integrity.
2. We will not falsify information, and clear signatures on each page will hold witness.

Decision-Making

1. We will use Matrix charts to facilitate our decisions on making different ideas that may conflict among the members in the team.
2. We will complete our individual tasks on time, in a manner which is not a hindrance to other team members and give notice at least 3 days in advance if problems arise or the task cannot be completed.
3. We will contact each other outside of class at least once a week to make sure deadlines can be met and any problems risen can be solved
4. Will be realistic when choosing our goals and group deadlines.