Archive for the 'Team Codes of Conduct' Category
Code of Conduct Assignment

As a team working on Prototype I or II, write a Code of Conduct.

  • due midnight before September 18

Gory details

Code of Conduct: Team 9 – Remote Piano Pedal

Last Revised: 16-Sep-12 : 1.00pm

Code of Conduct:

While working on Project “Remote Piano Pedal”, all members of “Team 9” have considered and agree:

  • Work closely and transparently.
  • Keep healthy communication.
  • Attend all meetings on time and come prepared.
  • Write meeting minutes.
  • Listen and show respect to the team members and their ideas.
  • Constructively criticize ideas not persons.
  • Don’t let frustration turn into a personal attack. Solve conflicts sensibly.
  • Distribute tasks equally and complete them by the due date.
  • If a member is not able to finish work by the due date, inform other members in advanced.
  • Do not hesitate to ask for help.
  • Decisions will be made after considering all the team members’ opinions.

Meeting times and locations

  • Tuesday 9am Library/Sr Design Lab
  • Tuesday 7pm Sr Design class
  • Thursday 9am Library/Sr Design Lab

Team Members

Tom Tasker, Atul Gaikwad, James Mureithi

Code of Conduct: Team Alpha – TrueView Power Chair Camera System

Last revised [9/17/12]

Code of Conduct:

Captain: Eric Robinson

Reporter: Hiep Nguyen

Devils Advocate: Brady Randall

Project Manager: Seth Schoming

Operating Rules: There will be a 5 minute grace period for meetings and if you are going to be more than 5 minutes late just text someone within that 5 minutes that you will be late. We will meet and set up a plan for what to do and what needs to be done in the allotted time. We will have a schedule for when we need stuff done but that will change based on if things take longer than expected. We will not take notes but we will have a set schedule that needs to be followed. We will have laid back meetings where everyone is welcome to give their input and nobody’s opinion has more than the next person. Anything related to the project will be agreed upon by the group not just one individual. If the group is indecisive then Eric Robinson will make the final call as the captain of the group.

      We will meet at the least once a week for an hour or two as a group to discuss what each one of us has done and to help steer the group towards the final goal which is to better the lives of people with Cerebral Palms. We all have classes together so we will be in constant contact but emailing will be another form communication. Each person should be working on the project to finish on time but most of it will be as a group. If most of the members work on the project for 2 hours then the remaining members are required to put 2 hours into the project as well.

      Typical meetings should be where we all get together and talk about what has been done, if we are on schedule (and if not how to fix it), and what we have left to do. We will be in constant contact with a resident and her name is Marina so we will keep her informed on all progress made so that we do not make something that will be useless to them. Eric will spread out what needs to be done and who is doing it. If someone finishes early it would be helpful to help someone else out to finish what they are working on so that we can get this project done as fast and efficient as possible. Any questions or concerns about this document or the project will be discussed as a group.

Code of Conduct: Team 5 – Personal In-Home Rescue Lifter A.k.a The PIRL5000

Last revised 09/17/2012

Code of Conduct:

While working on Project Personal In-Home Rescue Lifter A.k.a The PIRL5000, all members of Team 5 have considered and agree:

General goals:

    • Create a product that meets the needs of a client
    • Create a product that meets or exceeds the clients specifications
    • Learn new skills and information
    • Learn how to work in a team environment
    • Complete tasks assigned on a schedule
    • Learn how to break large projects into smaller components and tasks and make all the smaller components work together as a single unit

Operating Procedures:

    • Team members will meet twice a week when needed at the following times or as otherwise scheduled by the team.
        • Wednesday 7pm – 9pm
        • Sunday 7pm – 9pm
    • Meetings will be for the following
      • Progress reports
      • Present completed work
      • Coordinate separate components
      • Raise issues
      • Solution discussions
      • Assigning the next tasks
    • Attendance to team meetings is essential but the team recognizes that there are reasons a team member might not be able to attend a meeting.
    • If a team member is not present at a meeting, the team member needs to
      • check the meeting notes and check with the other team members to make sure they understand what the team discussed and accomplished during the missed meeting.
    • If a team member is going to miss a meeting or be more than 10 minutes late, the team member should
      • notify the other team members by email a minimum of 2 hours before the meeting time if possible.
      • OR if the 2 hour email is not possible, the team member should call one of the other members to let them know that they will not be at the meeting or will be late.
    • Meeting notes will be taken at all team meetings.
    • All team members will take their own notes. The individual team member notes will be compiled and posted on the forum.
    • Meeting notes will include the following.
      • Important information shared with the team
      • Tasks and who is responsible
      • Decisions made at the meeting
      • Issues or problems
      • Solutions discussed
    • Meetings will be scheduled or cancelled no less than 24 hours in advance of the meeting
    • Meetings will be at times appropriate for all attendees
    • Each team member must be involved in group discussions
    • All project scope decisions will be made by the entire group by simple agreement or vote
    • Communication will be done using email and the team forum

Team Culture:

    • Every member is responsible for the team’s progress and success
    • Listen and show respect for the contributions of others
    • Be an active listener
    • Criticize ideas not persons
    • Feedback should be constructive
    • Everybody participates
    • No one dominates
    • All team members are equal in importance
    • All ideas considered equally
    • Ask questions when you do not understand
    • Accept and respond to feedback objectively
    • Acknowledge, and listen to, all other team members’ comments
    • Keep the team updated on progress regularly

Team Members:

Each of us as individuals in the team, have put our name and title below, showing that we have carefully reviewed and agree to the Code of Conduct as it stands in this document:

The initial roles of each team member are shown below. It is our plan to rotate each team member into all of the roles.

  • Captain- Christopher Eldridge
  • Project manager – Waleed Shaban
  • Skeptic – Richard Richey
  • Reporter – Kiet Nguyen
  • Entrepreneur – Neal Hockersmith

 

Code of Conduct: Group 3 – Rollover Protection Arms

Last revised 9/17/2012

Code of Conduct:

While working on the Rollover Protection Arms, all members of Group 3 have considered and agree:

Roles and Definitions

Todd Skelton – Reporter 

Mohammad Alharbi – Cynic

Saed Almajdoubah – Captain

Merl Don – Project Manager

Operating Rules

 

  • Everyone on time within 10 minutes of scheduled meetings
  • Everyone shares an equal part in the project
  • Everyone will complete the part assigned to them on time
  • Everyone needs to contribute to the meeting with their thoughts and ideas
  • Inform the group when you cannot make it to a meeting a day in advance

Meetings

  • We will meet twice a week.  Once during the class time and another when everyone is available.

Team Members:

Each of us as individuals in the team, have put our name and title below, showing that we have carefully reviewed and agree to the Code of Conduct as it stands in this document:

Todd Skelton – Reporter 

Mohammad Alharbi – Cynic

Saed Almajdoubah – Captain

Merl Don – Project Manager

Code of Conduct: MARZ – Campus App

Last revised September 17, 2012.

Code of Conduct:

While working on Campus App, all members of MARZ have considered and agreed on the following:

  • Do what you’re good at, but don’t pass something over because you don’t know how to do it. If a task isn’t readily taken, then nobody is an expert at it.
  • We may not always agree, but disagreement is no excuse for poor behaviour and poor manners.
  • If we decide to take a different approach than others, we will let them know early, document our work and inform others regularly of our progress.
  • Make an effort to research a topic yourself before asking for help. While we don’t want to waste time unnecessarily, this course is designed to push each of us outside of our comfort zones.
  • Document everything. We’ve been provided with several different methods of communication, and we’re all in this together. We don’t want to waste time doing redundant or unnecessary work. We also need to be able to consistently reference the work we’ve done. Be sure to document often so the rest of the group can work with your progress.
  • Every group member is entitled to input and is responsible for staying informed of current progress. If a member isn’t present for a decision or doesn’t speak up in a timely manner, they forefit their right to speak against a decision made by the rest of the group. Participation is both a requirement and a privilege.
  • Try to attend every meeting. If you cannot attend a meeting, let the rest of the group know. It is your duty to determine what you missed. (This can be done by reaching out to other group members, reviewing the minutes, and looking over forum posts.) Minutes will be kept at every meeting and posted on the forum immediately afterward.
  • Know your objectives for every week. This ensures that our group is moving forward and that everyone is participating. If you do not know your objectives, ask other members and check the forums.
  • Write your programs to be robust and readable. Security and readability are essential in any group program. Comment on obscure portions of your work as you feel is necessary.
Code of Conduct: Out of Time – The Chill Pad

Last revised [9-18-2012]

Code of Conduct: Group 6

General Goals

  • To design a product that meets our consumers needs.
  • Work on developing team skills.
  • Gain a better knowledge of the design and creation process.
  • Earn service learning requirement for Engineers of 2020.

Rules

  • All members must communicate regarding meeting times.
  • All members should be relatively on time to meetings.
  • Member will contribute equally to the project.
  • Assigned tasks to each member will be completed on time.

Conduct

  • All members treat each other with respect and dignity.
  • Members will accept criticisms with an open mind.
  • Team members will help each other when needed or requested.
  • Team members will not break out in random fist fights for any unnecessary reasons.

Meetings (most likely times)

  • Monday evenings
  • Tuesdays class time

Roles: N/A

Code of Conduct: Infinite Loop – Heating and Cooling Seat Cover

Goals

  • Develop a product that will not only display engineering expertise but also positively impact the lives of our customer base (CPRF community) based on its effectiveness, ease of use and economic viability.
  • Fully utilize every group member’s knowledge and strengths
  • Develop a team mentality and dynamic that will prepare team members for future career projects.
  • Get an A in the course and ultimately come out with a resume booster.

Rules

  • All decisions must be unanimously agreed upon.
  • At least 2 day prior notice should be given if a member cannot attend a group meeting.
  • Members are encouraged to show up before the scheduled times but a 5 minute window will be allowed.
  • All criticisms and opinions will be presented respectfully, and thus viewed positively.
  • All members will take full responsibility for completing their designated tasks
  • Meetings will adjourn only after all members are satisfied and agree that all matters have been discussed.
  • All team members must partake in group discussions.
  • The team will come up with weekly goals and ensure all goals are met.
  • Each team member will act as both a teacher and student.
  • The roles will change monthly and it will be the responsibility of the current project manager to designate weekly roles and tasks to the team members.
  • All weekly tasks will be spread out four ways and only after all members agree that there’s a balance will the tasks be designated, to ensure equal work load.
  • The team will take a utilitarian approach in all matters.

 

Roles Definition:

  • Leader:  Delegates the positions for the month.
  • Reporter: Take notes during meetings so persons who missed can be brought up to speed.
  • Project Manager:  Keep in check with persons on their tasks, help keep things moving.
  • Researcher:  Look for solutions online for snags, or potential helpful items for problems.

Meeting schedule

Monday  -  7:00 pm  -  Ablah Library basement

Tuesday  -  7:00 pm  -  Wallace hall

Saturday  -  1:00 pm  - Ablah Library 24hr room.  (if need be, based on task and group consensus)

Meeting objectives

Monday meetings

  • Compile all task outcomes and complete assignments.
  • Ensure all goals were met
  • Discuss on lessons learned and adjustments that need to be made for better outcome.

Tuesday meetings

  • Meet with instructor
  • Come up with week’s goals and tasks
  • Set the different deadlines for each task, if sequential.

Saturday meetings

  • Fill each other in on progress of individual tasks
  • Members ask for assistance if they are having trouble.
  • Redistribute tasks if need be.
  • Evaluate to determine if deadline have been or will be met.
Code of Conduct: Team 12 – Home Automation Framework

Code of Conduct

 

While working on Project Home Automation Framework, all team members of

Team Twelve have considered and agreed:

Roles and definitions
Captain:  

  • Oversees all issues involving the project and the Team.
  • Ensures each team member has a clear understanding of the Project and their role.
  • Coordinates and advises other leaders (i.e., Liason, Perfectionist, Technical Wizard, Business Advisor) to achieve task completion.
  • Encourages the Team as a whole to make contributions and keeps team members active and engaged.
  • Develops agenda for meeting, minutes after the meeting, and organizes all documents and communications within the team in a manner that provides easy access for all team members. Captain has the right to delegate any of these tasks at his discretion.

Liason:

  • Coordinates communication with outside parties
  • Reaches out to other teams for collaborative efforts.
  • Interacts with marketing target group.
  • Liason has the right to delegate any of these tasks at her discretion.

Perfectionist:

  • Oversees writing and editing of all Project reports.
  • Provides constructive feedback and criticism of project ideas.
  • Directs testing, debugging, and other methods of feedback.
  • Perfectionist has the right to delegate any of these tasks at her discretion.

Technical Wizard:

  • Oversees and handles all technical aspects of the Project including budgeting and procurement of equipment.
  • Coding, structuring, soldering, and other mechanical activities required for the group pass through him/her.
  • Technical Wizard has the right to delegate any of these tasks at his discretion.

Business Advisor:

  • Analyzes the marketplace in order to better guide the Project towards the goal of market implementation and adoption.
    • Assess marketplace valuation of the Project in order to establish a cost goal for the Team and Project.
    • Ensures the Project contains features and benefits consistent with marketplace needs and/or wants.

Rules of Operation

  • Meetings:
    • Sunday Meetings
      • The team shall meet on Sundays from 4:00 to 5:30 p.m. at the library unless otherwise agreed upon by the Team.
      • The objectives of Sunday Meetings are:
        • Work on collating, perfecting, and submitting work.
        • Decide on tasks to be done during the week
        • Discuss progress in ongoing tasks.
      • An agenda for each meeting should be developed by The Captain
    • Thursday Hangouts
      • The team shall meet on Thursdays from 8:00 to 8:20 p.m., unless otherwise agreed upon by the team, via Google+ Hangout.
      • The objectives of Thursday Hangouts is:
        • Ensure everyone is okay with their tasks,
        • Ask for help if needed, and
        • Remind everyone of any ongoing tasks or future deadlines.
  • Personal Requirements:
    • Each team member has to be a good listener by showing respect to the person speaking.
    • Each member contributes to the Team and must accomplish his or her work to meet deadlines.
    • Each member shall be informed about their respective portion of the project.
    • Members shall be respectful of other people’s times.
      • If a member will be late, or missing, to a meeting, he/she should give as much notice as possible, so we are not waiting.
      • If there is quorum for a meeting, the meeting will start with or without missing members at most 15 minutes later than scheduled time.
  • Communication Requirements:
    • All members shall be free to express his or her ideas without fear of ridicule or persecution.
    • Constructive and polite criticism is encouraged.
  • Decision Requirements:
    • Decisions need to be approved by at least 3 members of the group.
      • All Members do not need to be present during voting.
      • Therefore, 3 members will be considered quorum for an official meeting.
    • All major ideas, decisions, and discussions need to be documented on the meeting Minutes and available to all members.
      • This includes: Meeting Agendas, Brainstorming Sessions, Voting on Decisions, And other types of discussions

Changes to Code of Conduct

  • The Code of Conduct will expire at the end of each semester. At this time, it will be reviewed again and voted upon before the beginning of the next semester.
  • The Code of conduct can be changed when all members are present, a potential change is presented to the Team, and shall require at least 3 votes for approval.

Team Members & Roles:
The Captain: Jose Crosa
Perfectionist: Olivia Fletcher
Liason: Nnennaya Udochu
Technical Wizard: Trey Thomas
Business Advisor: Mike Ditch

 

Code of Conduct: 7. Team Bravo Squad – Emergency GPS Locator

Last revised 9/17/2012

Code of Conduct:

While working on Project Emergency GPS Locator, all members of Team Bravo Squad have considered and agree:

  • General Rules
    • The team will use their knowledge and skills and any useful talents to complete any goals set before them
    • Listen to each other and gain a relationship of trust through our experiences
    • Manufacture a unique product that will impact the user in a positive way
    • Work efficiently together as a team, not being distracted by any work outside the goals of the project.
    • Taking responsibility for any individual work, and understanding the importance of individual work.
    • Be on time to the meetings, and notifying the team if they are going to be more than 5 minutes late.
    • Understanding each others strengths and weaknesses, and assigning work to the individual who has a strength in that field.
    • Understanding their own strengths and weaknesses, and to have the courage to ask for assistance when having trouble with an assignment.
    • Everyone will give a presented idea serious thought.
    • Everyone will act with respect.
  • Roles and Definitions
    • Chief Grunt is in charge of coordinating tasks and ensuring the project stays on schedule.
    • Grunts are in charge of finishing the work assigned to them by Chief Grunt.
    • The Business Magnate is responsible for maintaining client relationships, product promotion, and other things business magnates worry about.
  •  Meeting Times
    • Monday 7pm WH Senior Design Lab
    • TBD
  • What to Accomplish at Meetings
    • Summary of what was accomplished since last meeting
    • Review of distance to long term goal
    • Distribution of assignments
    • All key points summarized and posted on google docs for easy distribution within team

Team Members:

Each of us as individuals in the team, have put our name and title below, showing that we have carefully reviewed and agree to the Code of Conduct as it stands in this document:

  • Chief Grunt: Danny Nguyen
  • Grunt: Tanner Doshier
  • Grunt: Bryan Albrecht
  • Grunt: Ryan Clark
  • Business Magnate: Sydney Blanton