CompSci 308 Spring 2023 |
Advanced Software Design and Implementation |
Sometimes, you have to look back in order to understand the things that lie ahead. — Yvonne Woon
For this entry, 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.
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.
AND,
Submit a Markdown formatted plain text file, named week11_slogo_teamwork.md
, to the individual portfolio_NETID
repository provided for you in the course's Gitlab group.
Use this Google Form to review your teammates and yourself to determine who has been cooperative and proactive as well as helping 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.
In Markdown, 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:
ChatGPT can help you generate ideas, create example code, review, refactor, or even debug code. While you are not required to use it, if you do, I think it would be helpful to share our collective experiences. To that end, each week's Journal will include a place for you to share how you used ChatGPT in more detail than would typically be found when attributing it within your code or README file. I have also created an ED thread tag for ChatGPT. This exercise can also help you reflect on how to use it more deliberately and usefully.