Team Meetings

Planned Meeting:

Date	Type

Meeting Minutes:

Meeting Minutes 1: February 9 2023

Date	Start Time	End Time	Type	Missing Members
February 9th	6:00pm	7:20pm	Lab	N/A

Takeaways:

• Work on completing parts of every deliverable before meeting with the TA rather than completing an entire deliverable
• Divide tasks so that at most 2-3 members are working on the same task. It is inefficient to unnecessarily involve all team members in a simple task.
• Continue to ask questions when needed!

Meeting Minutes 2: February 16 2023

Date	Start Time	End Time	Type	Missing Members
February 16th	6:15pm	7:00pm	Lab	N/A

Takeaways:

• Address feedback for Project Part 2 deliverables as part of Project Part 3
• Prepare UML diagram for next meeting (March 2)
• Aim to finish everything for the halfway checkpoint (it's okay to leave more difficult user stories such as the map for Part 4)

Meeting Minutes 3: March 2 2023

Date	Start Time	End Time	Type	Missing Members
March 2nd	5:30pm	6:15pm	Lab	Aryaman Raina

Takeaways: Our TA mentor gave us feedback on our UML diagram

• 1 database class (merge PlayerDB and QRCodeDB)
• Don’t have more than 4 or 5 classes in a row
• Differentiate by layers (helps readability) ->Top: Activity, Middle: Controllers, Bottom: Model
• If something is deleted, other classes that are contained in a class are deleted as well.
• For lists, choose a consistent style. Either have a list in the class AND an aggregation/composition or just an aggregation/composition
• Need to have an inheritance somewhere (demonstrate that you understand the concept!) -> some ideas: TopPlayers, BestQRCodes, others...

To-do:

• We need to assign user stories to each team member
• Complete halfway checkpoint user stories before March 13th deadline. Don't forget documentation and test cases!

Date	Start Time	End Time	Type	Missing Members
March 9th	5:30pm	6:15pm	Lab	N/A

Alex was able to get assistance from the TA to resolve his issues with generating javadocs Takeaways:

• Start test cases ASAP. They can be time consuming to write
• Update UML diagram as the application evolves
• We are to demo our application using the code we submitted for the halfway checkpoint in next week's lab meeting. Be aware of any outstanding issues and be prepared to explain our code

To-do:

• Complete halfway checkpoint user stories before March 13th deadline. Don't forget documentation and test cases!

Meeting Logs:

Date	Start Time	End Time	Type	Missing Members
February 8th	2:00pm	4:40pm	In person	N/A

Topics discussed:

• Designed rough draft of UI design
• Planned app functionality and how we intend to implement user stories
• Discussed each user story as a team and determined their risk level and story points
• Assigned roles for UI design, Project backlog and wiki, and CRC cards amongst pairs
• Planned our next meeting to be Saturday, Feb 11th

Date	Start Time	End Time	Type	Missing Members
February 11th	3:00pm	4:00pm	Call	Advik Mehta

Topics discussed:

• Reviewed UI design as a group and gave feedback
• Reviewed CRC cards as a group and gave feedback
• Assigned roles for story board flow diagram and page description
• Discussed goals for half way check point
• Planned our next meeting for tomorrow, February 12th, with hopes of finalizing Project Part 2

Date	Start Time	End Time	Type	Missing Members
February 12th	8:00pm	9:00pm	Call	N/A

Topics discussed:

• Discussed storyboard use case flow
• Reviewed UI design as a group and gave feedback
• Reviewed CRC cards as a group and gave feedback
• Chose user stories to be completed by half way checkpoint
• Discussed what each member needed to work on before the deadline

Date	Start Time	End Time	Type	Missing Members
March 5th	7:30pm	8:10pm	Call	N/A

Topics discussed:

• Assigned user stories to each team member (see Sprint Review 1)
• Test cases are to be created by members responsible for the user story the test case verifies (eg. the test case for adding a QR code to a player's account should be made by the same person who implemented adding a QR code)