Weekly Journal : OOGA Team Review

It’s a curious thing about our industry: not only do we not learn from our mistakes, we also don’t learn from our successes. — Keith Braithwait

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 as well as how you have grown as a team mate during the semester.

Submission

Submit a Markdown formatted plain text file, named week15_ooga_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 help us understand your personal view of the project's planning and progress. Your evaluations will let us know how their teammates view other's contributions to the project so we can better understand the objective evidence we have that may be missing context (if nothing is reported, then we will assume the worst). We are also looking to see if you have responded to earlier feedback you received in an effort to improve as a teammate. 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, game, player, 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?
  • What roles beyond coding have you taken on and how did that helped the team?
  • Who generally took on work "between assigned responsibilities" and was that positive or negative for the team?
• 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 semester?
  • What specific thing can you do to ensure successful team outcomes in the future?