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.

  • Prototype I: due midnight before September 16
  • Prototype II: due TBA

Gory details

Code of Conduct: Team Alpha – The Smart Mailbox

Last revised Sep 15th
 2011

Code of Conduct:

While working on Project [The Smart Mailbox], all members
of [Team Alpha] have considered and agree:

  • Every member of the team will attend every meeting, prepared and willing to give all
         possible helpful participation.
  • Every membe will do all the work assigned to him or her in the best way possible and
         within the time frame.
  • To maintain an atmosphere of cooperation and acceptance for each member in the team in
         meetings and while doing any related work.

 

Roles and  definitions

  • Captain:  Should be the
    general coordinator of the project, make sure everyone participate in the
    project, no member is doing much more or less than other members.
  • Reporter: write and keep reports for each meeting, write and deliver
    the final report.
  •  Cynic: in every meeting
    should bring reasonable counter arguments and look for what might be obstacles
    that should be taken into consideration.
  •  Project Manager: make sure
    everything go with the planned time frame and no important details are left
    behind.
  • Technical reporter: keep records for all important technical
    information, technical errors and obstacles and how the team managed to
    overcome them.

Operating Rules:

  • All Meetings are conducted under WSU rules of conducts.
  • Starting from meeting one, the team makes an agenda for what’s
    going to be done during the next week and what to discuss in the next meeting.
  • The reporter will keep record for minutes of the meeting.
  • Every member should leave the meeting room knowing exactly what he
    or she is supposed to do till the next meeting.

Number of Meetings

  • There will be one general meeting every Friday at 1:30 for 2
    hours.
  • The meeting to be in Ablah Library, the project manager reserve a
    room in advance and send e-mail to all members one day at least before meeting.
  • The team agree on what every member should do, the reporter send
    the full report to all members through e-mail.

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:

  • Captain: Said   Alyami
  • Reporter: Jessica  Bever
  • Project Manager:    Festus Okoth
  • Skeptic: Kathy
  • Technical Reporter: Stanley
    Okafor
Code of Conduct: Samov – Touch Projector

Last revised 09/15/11

Code of Conduct:

General:
During our Touch Projector Project, all members of Samov have considered and agree to:

  • Attend every meeting, mentally awake, and on time
  • Motivate each other, and maintain enthusiasm for project
  • Listen respectfully to other member’s inputs
  • Come prepared to each meeting
  • Actively communicate outside of meeting times for project’s progress
  • Do all work required or needed for project’s progress
  • Come to solutions as a group
  • Maintain peace with open atmosphere and encouragement of ideas
  • Strive for overall success

Operating Rules:
During our meetings, all members of Samov have considered and agree to:

  • Create agendas
    • Beginning-of-meeting agenda
      • List of what we would want to get done during that day’s meeting
    • End-of-meeting agenda
      • List of what we need to get done for next week’s meeting. including specific tasks for each member
  • Notes to be taken by volunteer note-taker and e-mailed to everyone in group

Number of Meetings:
Estimated 5 minimum. Add more meeting times if determined to be needed.

  • Meeting with project advisor at 1:45 PM Fridays (15 minutes/Friday)
  • Meet with group right after. Last until agenda completed. (total about 10 hours+)
  • Individual work outside of meeting (time spent as needed to achieve project goals)

Meetings conclude with mutual understanding of what needs to be done and motivation.

Team Members and Roles:

**We 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:

  • Captain: Stephen
  • Vise-Captain/Reporter: Mimosa
  • Manager: Veena
Code of Conduct: HTC (not the phone company) – Pedal Pal

Last revised [09/15/2011]

Code of Conduct:

While working on Project [Totally freaking Awesome AKA Digital Synth Control], all members of [Totally Awesome] have considered and agree: (Chris Cenatiempo, Taylore Eisenhauer, Haider Ali Malhi

  • Team meetings will happen on Friday during scheduled class times and Tuesday at 4 30
  • Friday will be building and  Tuesday will be organizational
  • Each person will be assigned part of the programming
    • Roles will be determined in an ongoing manner
    • Taylore will take audio recordings of Tuesday meetings and everyone will take personal notes for Friday meetins
    • Every member is responsible for the team’s progress and success
    • Attend all team meetings and be on time
    • Come Prepared
    • Carry out assignments on schedule
    • Listen and show respect for the contributions of others
    • Be an active listener
    • constructively criticize ideas not persons
    • only one person speaks at a time
    • everybody participates, no one dominates
    • respect those not present
    • ask questions when you do not understand

 

 

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:

  • Captain: John
  • Reporter: Mr Harrison
  • Project Manager: Prof John
  • Skeptic: The musician formerly known as John Harrison
Code of Conduct: DSSP- Smart Mailbox for Smart Wheelchair

 

Code of Conduct:

 

While working on the project Smart Mailbox for Smart Wheelchair, all members of DSSP have considered and agree:

 

  • Every member needs to attend every meetings on time
  • Members need to be prepared in their topics assigned
  • Work as a team rather than individually
  • Be an active listener
  • Be a leader, not a boss
  • Do not offend any members of the team
  • Share ideas and ask questions if not clear
  • Have fun and be excited about the project!!
    • Roles and definitions 
      • Captain:  Pravin Maharjan……   Lead the team towards our goals.  Generate enthusiasm among team members and work with everyone towards completing an excellent project.
      • Reporter: Dipendra Khatiwada….Absorb ideas and thoughts and convey them in words.  Make sure that the team is following timelines by keeping every details on paper.
      • Project Manager: Suman Gautam……Come up with ideas that will establish better understanding of the project.  Also, think of ways to make the project unique and add ideas to keeping it feasible, marketable, and useful.
      • Skeptic/Cenic: Santosh Shrestha…. Be the one that keeps a close eye on things that might not work for the team.  Provide appropriate criticism and ideas that will help the team on deciding if the project is going in the right direction. 
    • Operating Rules
      • We are planning to use Google Blog for the team to share ideas and keep a track of everything we do.
      • We will be conducting team meeting in person and also using our blog.
      • The reporter will be taking notes of what is going on during the meeting and outside the meeting if needed.
    • Number of Meetings
      • We will be having team meetings at least two times a week.  We will also be sharing ideas using emails, blog, etc. 
      • Our team will work at least 3-4 hours a week individually on their assigned role/assignment so that we can achieve the set goal.
    • What should be typically accomplished in a meeting? 
      • We will decide on a specific topic to talk about during the meeting so that the meeting becomes valuable.
      • We will meet and share ideas that might make the project better
      • After we come to a final decision on what project we will be doing, we will meet and start building our prototype.

 

 

 

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:

 

  • Captain:  Pravin Maharjan
  • Reporter: Dipendra Khatiwada
  • Project Manager: Suman Gautam
  • Skeptic: Santosh Shrestha


Code of Conduct: [Team Name] – [RC car controller sensor glove]


Code of Conduct:

While working on Project [RC car controller sensor glove], all members  have considered and agree:

  • Meeting Time:
                   -Team meeting will be held on every Monday 1:30-3:00, and friday after class project finish.  Also, additional meeting time will need depend on the project progress.
                   - Members can be late for the meeting, but need to notify other team members before the meeting start.
  • Meeting Discussion
                 -Review last meeting info.
                 -Discuss the project progress
                 -Discuss any issues each member had and find the solution.
                 -All members expect to participate in discussion
                 -Discuss current week assignment.
                 -Ask questions
                  -Team works
  • Before Meeting End
    • An outline and assignment will be giving to each member to complete.
    • Must prepare for the next meeting.
    • Last but not least all member expect to “Play hard” but “Work even harder”.

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:

  • President: Giang
  • Project manager: Haymar
  • Reporter: Phuong
  • Worker: Now Hiring
Code of Conduct: Team Name – DoorTextChecker

Last revised September 14, 2011

Code of Conduct:

While working on Project DoorTextChecker, all members of  Team Name have considered and agree:

Team Meeting Time

  • Wednesday Nights around 7:00 pm
  • Friday Afternoon after group meeting
  • 1 – 2 hours per meeting
  • 1-2 hours a week for individual work time
  • Meeting plans
    • Review workloads
    • Go over status of each person’s assignment
    • Establish goals for next meeting
    • Work on any collaborative work or schedule additional time for it. 

Team Roles

  • Software Tech – general programming and api – Jordan Castillo
  • Hardware Tech – wiring and electronics – Matt Price
  • Arduino,Xbee,Networking Tech – Todd Thimmesch
  • Everyone will act as a leader, if one fails we all fail.

Rules

  • Be there on time.
  • Notify the team if unable to make it.
  • Don’t be stupid, there is such thing as a stupid question.
  • Use common sense for all other rules.

Game Plan for Prototype 1:

  • Get two wireless recievers to talk to each other
  • Be able to tell a switch status, on or off
  • Be able to use email to check this

 

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:
  • Software Tech – Jordan Castillo
  • Hardware Tech –  Matt Price
  • Arduino,Xbee,Networking Tech – Todd Thimmesch
Code of Conduct: Team GTLE- RF signal enhancer

9-19-11

Code of Conduct:

While working on Project , all members of [Team Name] have considered and agree:

  • We will meet every Monday and Wednesday at approximately 5:30. Certain Saturdays will also be required. Full notification of an absence from a meeting will be required at least 1 day in advance.
    • *Whereas in the case of three of more absences without notification, immediate expulsion from the team will be enforced.*
    • In addition, it is up to the teams’ discrepancy after one absence without notification about what the consequences shall be.
  • As far as information or materials gathering, i.e. contacting a company for information, all ideas or requests will be put forth through the captain before any arrangements are made.
  • Because this project can be multi-dimensional after a certain stage, each member is expected to stay on task through the early developmental process as to not leave any member behind.
  • Every person in the group is expected to document information uncovered outside of group meetings that will be helpful to the project. This includes  citing sources from which the information is pulled and taking detailed notes in order to fully regurgitate this information to the group at the next meeting.
  • During group meetings, it is expected that every member fully participate and take an active role (whether that be to push the project forward or to understand what has been uncovered more) in the task at hand.
  • Every member is responsible for the team’s progress and success
  • In addition to the above mentioned formalities, certain intrinsic behavior includes:
    • Attend all team meetings and be on time
    • Come Prepared
    • Carry out assignments on schedule
    • Listen and show respect for the contributions of others.
    • constructively criticize ideas not persons
    • everybody participates, no one dominates
    • no rank in the room
    • respect those not present
    • ask questions when you do not understand
  • In this group, it is to be understood that if one falls behind the others, whether it be due to lack of inquiry or irresponsibility, it is that person’s responsibility to make sure and get caught up with the group. That is, every group member is expected to help the other, but unless one that has fallen behind takes the initiative to get caught up, the blame is solely on themselves.

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:

  • Captain: Bart Voegeli
  • Muscles: Guner Yilmaz
  • Brains: Shaun Golden
  • Reporter: Eric Nyaga
Code of Conduct: The Mind Takers – Mind Controlled RC Aircraft

Last revised [9/14/11]

Code of Conduct:

While working on Project Mind Controlled RC Aircraft, all members of The Mind Takers have considered and agree:

  • Operating Rules
    • Meetings will occur once a week at 10am on Mondays
    • Order of business is as follows:
      • Review previous meeting notes
      • Discuss old business/Update old action items
      • Discuss new business/Create new action items
      • Project progress review
      • Project discussion free-for-all
      • Meeting Adjourned
    • Each team member is responsible for working at least 2 hours individually each week on the project unless specified otherwise
    • Ideally there will also be a 2 hour joint working session on the project with as many team members as can make it
    • Every member is responsible for the team’s progress and success
    • Attend as many meetings as possible and try to be on time
      • Let team members know if you’ll be late or miss a meeting
    • Have all of your work and notes prepared
    • Keep on schedule as much as possible
    • Listen and show respect for the contributions of others
      • Be an active listener
      • Criticism should be constructive
    • Only one person speaks at a time
    • Everyone should participate
    • Respect all team members
    • Always ask questions when something isn’t understood
    • Don’t be afraid to voice ideas

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:

  • Captain: Eric Berman
    • With project manager, ensure the project is making progress and following the timeline
    • Delegate responsibility of different tasks to each team member, including the Captain
  • Reporter: Ifeanyi Bruno Umeadi
    • Organize individual progress reports into a unified document
    • Report on overall progress of the project
    • Take meeting notes
  • Project Manager: Kalyn Kovac
    • Certify that the project is on schedule
    • Review each team member’s progress report before sending it to the reporter
  • Skeptic: Eric Berman
    • Predict possible problems with the project and work with other team members to create solutions
    • Take meeting notes