You each should individually maintain and update a weekly log book. You are advised to continuously update your log book.
To this end, create a single team log book in which each team member adds the main activities that s/he worked on during the project. We recommend that you use a simple text file for this that can be shared with all team members and add it to your Git repo. This will also make sure your TA has access to your log book from the start of the project.
Structure: structure this log book into weeks (create a Week 1, Week 2, etc. heading), and add individual team member sections by adding your full name for each week.
Content: Maintain a simple list of bullets with brief but specific descriptions of each activity that you worked on that fit on 1-2 lines max (do not write paragraphs). You should think about all the different things that should be worked on such as coding, modifying, updating, testing, designing, analyzing, writing, etc. Each item (bullet) in your log book should have the form: <bullet><date>: <activity-description>, where the activity description should start with a verb (indicating what you did). Some good examples would be:
7-1: Created the Dialogflow agent, downloaded the JSON key file, and updated the flowkey and flowagent parameters in the
.mas2gfile.7-1: Updated the Prolog rule for applyFilter for the cuisine filter.
8-1: Tested the addFilter intent and added new training phrases to make it more robust.
The log book will be used to evaluate your participation as a team member within the team. We can use this as a basis for making individual grade differences at the end of the project.