After the first reflection report, each subteam for design will create a weekly "minutes" (due every Friday at 5PM) made up of bullet points detailing, as specifically as possible:
Accomplishments for the week
- What is the status of your work (not started, coding in progress, coding complete, tested, annotated, variables added to Variable Naming Guide, etc)?
- What specifically did you work on (did you meet with Monroe, your Team leader? did you spend time understanding a file or function? did you complete code?)
Difficulties/Challenges
- What did you get stuck on? Are you having difficulty using a particular file or function? Do you have a specific bug?
Goals for the coming week
- Have you scheduled a meeting with someone? Are you planning on getting a specific piece of code fully written? Are you going to finish testing for bugs?
In addition to the above bullet points, groups of more than one should also submit a paragraph describing how the team is working together. The purpose of this section is to assess your efficiency, productivity, and how well you are learning.
- Are there concepts or ideas that your team needs help with?
- Did your team accomplish what you set out to do?
- If not, what reasons can you give? Was it team dynamics, computer failures, communication between the TA or professor, a lack of understanding in some concept, or is it something else? Be very specific here so we can help your team as much as possible.How you are tackling problems (who you are talking to)
This weekly summary is meant to show us the basics of what you are working on and to help you focus in on specific problems that you encounter that you have not yet been able to resolve. Ensure that you review the Design Philosophy when working on your design code. It is your responsibility to indicate how you are going to submit these reports whether it is from an e-mail from word or in a google doc.