User:Melissa Ko/Notebook/oncoCURES/TeamInfo

From OpenWetWare
Jump to navigationJump to search
oncoCURES <html><img src="/images/9/94/Report.png" border="0" /></html> oncoCURES Home

Team Contacts

Note: Email is always preferred for contact.

Melissa Ko

  • email: mesako@mit.edu
  • cell: 408-839-2512
  • dorm: East Campus
  • availability: MTWR6, F4, S2, SU6

Nick Myers

  • email: njmyers@mit.edu
  • cell: 210-387-4218
  • dorm: Theta Xi
  • availability: ???


Team Contract

Part 1: Goals

  • What are the goals of the team?

Team Goals: to create an inexpensive treatment for cancer with long-lasting impact that can substitute current more-damaging therapies such as chemotherapy and radiation

  • What are your personal goals for this assignment?

Personal Goals: to gain a new understanding of biology specifically relating to cancer, to develop problem solving skills that relate to experimental bioengineering, to learn about the working parts that make up synthetic biology systems

  • What kind of obstacles might you encounter in reaching your goals?

Obstacles: need a thorough and complete understanding of cancer, complications due to systems, efficiently processing all of the current technology and research available

  • What happens if all of you decide you want to get an “A,” but because of time constraints, one person decides that a “B” will be acceptable?

The response to this is contingent on the circumstances, but because this project is team-based and results in a shared overall grade, it will be expected that each team member will do his or her assigned work to support the rest of the team.

  • Is it acceptable for two or three team members to do more work in order to get an “A” ?

Everyone is free to do more than their share of work if they so choose to, however, everyone is expected to do his or her part (a certain minimum amount).

Part 2: Meeting Norms

  • Do you have a preference for when meetings will be held? Did you have a preference for where they should be held?

Meetings will be held based on the listed availability. The location will be chosen for everyone's convenience, but will likely be an empty classroom on campus.

  • How often do you think the team will need to meet outside of class? How long do you anticipate meetings will be?

Meetings will be at least once a week, and likely last for one hour as the team checks up on each other and looks at individual assignments and current progress.

  • Will it be O.K. for team members to eat/email during meetings?

It is perfectly fine for team members to eat and email during meetings as long as work is done and the team is productive.

Part 3: Work Norms

  • How much time per week do you anticipate it will take to make the project successful?

With the unit distribution, it is fair to expect each team member to do 3 hours per week. This will change with coming deadlines and depending on obstacles.

  • How will work be distributed?

Evenly.

  • How will deadlines be set?

Deadlines will be set to match those of the class. In addition, there will be team/individual deadlines that are specific to our project that will be listed elsewhere on this wiki.

  • How will you decide who should do which tasks?

Work will be delegated based on interests, strengths, and time commitment, while still being divided evenly.

  • What will happen if someone does not follow through on a commitment (e.g., missing a deadline, not showing up to meetings)? What will you do if one or more team members are not doing their share of the work?

This will lead to some conferences to discuss how to deal with the problem or the cause of this trend, plus some planning ahead to prevent this from reoccurring in the future.

  • How will the work be reviewed?

All individually done work will be reviewed by the other members of the group. Feedback will be given and appropriate improvements will be made once a consensus is reached. Also, the team will consult with the team mentor, Rebecca Adams, on bigger decisions for some critiquing.

  • What happens if people have different opinions on the quality of the work?

If someone is willing to offer improvements, they are free with the other members' permission to go the extra mile on an assignment. If the quality of work is indeed sub par, then the team should agree to rework the material and make it presentable. However, if different opinions mean a change of the overall idea, some discussion should precede any changes.

  • How will you deal with different work habits of individual team members (e.g., some people like to get assignments done as early as possible; others like to work under the pressure of a deadline)?

Assignments will be given with this in mind so time-sensitive work will be given to those who get work out of the way early, while dense, creative work will be given to those who need the pressure of a deadline to inspire good work.

Part 4: Decision Making

  • Do you need 100% approval of each team member before making a decision?

There needs to be a majority vote as well as a partially convinced opposition who is at least willing to go along with the decision so that team unity is not destroyed.

  • What will you do if one of you fixates on a particular idea?

The team will try to accommodate everyone's interests. Yet, if this particular idea is beyond the preference or expertise of the rest of the team, then it is fair that the member be expected to change their idea.



Retrieved from "https://openwetware.org/mediawiki/index.php?title=User:Melissa_Ko/Notebook/oncoCURES/TeamInfo&oldid=294844"