Weekly Journal : Cell Society Team Review

Sometimes, you have to look back in order to understand the things that lie ahead. — Yvonne Woon

For this entry, even though the project is not quite done yet, take a some time to reflect on the project's planning and progress, by analyzing your own role and the roles each person assumed in the team (describe actions, not personal qualities or personalities) and drawing conclusions about how the outcome could be improved in the future.

Submission

Submit a Markdown formatted plain text file, named week10_cellsociety_teamwork.md, to the individual portfolio_NETID repository provided for you in the course's Gitlab group.

Submit this Google Form, in which you will evaluate yourself and your other team member(s) as a tool to help improve everyone's experience with group work.

Specification

Peer Review

Review your teammates and yourself to determine who has been active and cooperative and to help those who have not improve for future projects. In general, your evaluations will not directly affect other members' final grade but will let members know how their teammates view their contribution to the project so they can adjust effort and behavior as needed (if nothing is reported, then it will be as if everything was as good as possible). It is their response to feedback, whether or not effort is made to improve as a teammate, that will affect the final grade. To give everyone the best chance for success, please rate your team members as honestly, accurately, and consistently as possible.

Teamwork Reflection

Discuss the effectiveness of your team's communication, cooperation, and planning. Describe specific, impactful, events during the project to justify your comments rather than general terms like "always late", "writes bad code", etc. For example, a better description would be "Look at commit XXX, it was three days after it was promised (in an email/chat or a public meeting) and it did not work with the current version of the code so it broke the build."

Use the following questions to guide your reflection:

• Think holistically about everyone's contributions (such as facilitator, designer, refactorer, debugger) as well as the code you worked on (such as data, simulation, JavaFX expert, or generalist that helped out all over):
  • Describe your role(s) on the team. How satisfied are you with them?
  • Describe your team mate(s) role(s) on the team. How satisfied do you think they are you with them?
• Think about specific events during the project that either highlighted how well your team worked together or demonstrated a teamwork problem:
  • Describe when you felt the most satisfaction
  • Describe when you felt the team made the biggest leap ahead
  • Describe way(s) the team has worked well so far (especially things you think can transfer to future teams)
  • Describe problem(s) with the way the team worked together (especially warning signs, if any, that were there in hindsight)
• Think about working with others as a learning opportunity for you to improve:
  
  • What is your biggest strength as a team mate?
  • What is your biggest weakness as a team mate (yes, everyone has some weakness)?
  • What have you learned team collaboration/communication during this project?
  • What specific thing can you do to make team collaboration/communication more productive or enjoyable in the future?