-
Notifications
You must be signed in to change notification settings - Fork 3
Team Meetings
Alex Nguyen edited this page Apr 3, 2023
·
42 revisions
| Date | Type |
|---|---|
| Date | Start Time | End Time | Type | Missing Members |
|---|---|---|---|---|
| February 9th | 6:00pm | 7:20pm | Lab | N/A |
- 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!
| Date | Start Time | End Time | Type | Missing Members |
|---|---|---|---|---|
| February 16th | 6:15pm | 7:00pm | Lab | N/A |
- 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)
| Date | Start Time | End Time | Type | Missing Members |
|---|---|---|---|---|
| March 2nd | 5:30pm | 6:15pm | Lab | Aryaman Raina |
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...
- 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
- 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
- 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 16th | 5:10pm | 5:40pm | Lab | N/A |
We demoed our app in its current state to our TA mentor. Below is the feedback from the demo and outstanding issues:
- Have all test cases completed for Project Part 4
- GitHub actions is not set up to run test cases (workflow is not correct)
- Missing javadocs for some classes
- A less detailed version of QRcode page shows if a player does not have a QRcode (eg. no visual representation)
- Address Feedback
- Refine code base/Address issues on GitHub
- Comments
- Map
- Estimate Player Ranking
- QR Code Leaderboard
- Test Cases (Unit tests/Intent tests)
| Date | Start Time | End Time | Type | Missing Members |
|---|---|---|---|---|
| March 23rd | 5:00pm | 5:10pm | Lab | Advik Mehta |
| Aryaman Raina (lab conflict) |
Today we discussed the final presentation. Here are some notes about the presentation:
- Presentation is on April 6th during the lab session
- High percentage of mark in Project Part 4
- 4 minutes
- In front of whole lab
- All members must be present
- Professors sitting in front of classroom as customers
- Interact with audience and be audible
- Discuss features, why someone should download app
- Should present user stories in a planned order
- Realistic data (need to get rid of test players for presentation)
- Save extra features for the end and present them if there is time
- No need to show non-essential features such as log in
- Arrive early to test laptop with projector (a team member must use their laptop for the presentation)
- Some teams use two devices (emulators) to show interaction between multiple users
- Some teams use their physical Android phone in their presentations. Look into FlyDroid to record app on physical device
- Record all user scenarios as pre-recorded video in case presentation goes wrong
General:
- Feedback on Part 3 will be made available by Monday (mostly UML feedback)
- Try to finish as much as possible for next meeting to get final feedback before presentation
| Date | Start Time | End Time | Type | Missing Members |
|---|---|---|---|---|
| March 23rd | 4:00pm | 4:30pm | Lab | |
- The TA answered some questions we had about the presentation
- Presentation Format: 4 minutes for presenting app, 1 minute to set up projector, 2 minutes for answering questions
- Members shared their progress on the user stories
- Clarification on Part 3 feedback
| Date | Start Time | End Time | Type | Missing Members |
|---|---|---|---|---|
| February 8th | 2:00pm | 4:40pm | In person | N/A |
- 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 |
- 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 |
- 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 |
- 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)
| Date | Start Time | End Time | Type | Missing Members |
|---|---|---|---|---|
| March 11th | 10:00am | 8:00pm | In person | N/A |
Note that not all members were present for the entire meeting
- All user stories for halfway checkpoint were completed in this meeting
- Team members gave feedback on each other's work
- Team members helped other members debug
- Scheduled a meeting for March 12th to debug outstanding issues, address outstanding feedback on Part 2, finish UML, write test cases
| Date | Start Time | End Time | Type | Missing Members |
|---|---|---|---|---|
| March 12th | 10:00am | 10:00pm | In person | Advik Mehta (worked remotely) |
| Aryaman Raina |
Note that not all members were present for the entire meeting
- Tests for user stories implemented and model classes were written (Advik, Alex, Logan, Sukhnoor, Vera)
- Debugged outstanding issues (Alex, Logan, Sukhnoor, Vera)
- UML diagram while not complete sufficiently communicates the current state of the app (Alex)
- Feedback on Storyboard/Screen Descriptions was addressed (Logan)
- Verified that GitHub page (main branch) has the correct version of the app
| Date | Start Time | End Time | Type | Missing Members |
|---|---|---|---|---|
| March 27th | 6:30pm | 7:20pm | Online | Aryaman Raina |
| Vera Maoued |
- Everyone reported their progress on the remaining user stories
- Group members asked questions about areas of uncertainty:
- How to restructure the database so only QR code names are saved in Player documents?
- How to implement maps as a Fragment rather than an Activity?
- Are Comments connected to Player or QRCodes?
| Date | Start Time | End Time | Type | Members Present |
|---|---|---|---|---|
| March 31st | 2:30pm | 5:00pm | In person | Alexander Nguyen |
| Logan Hepfner |
- Resolved merge conflicts on files we were both working on
- Logan continued to work on the comments feature
- Alex started working on the Map functionality (using the Google Maps API with no markers provided by Sukhnoor)
| Date | Start Time | End Time | Type | Missing Members |
|---|---|---|---|---|
| April 1st | 10:00am | 7:30pm | In person | Aryaman Raina |
- Map functionality fully completed
- Started working on UI tests for Part 4
- Improved the application UI
- Debugged outstanding issues
| Date | Start Time | End Time | Type | Missing Members |
|---|---|---|---|---|
| April 2nd | 10:00am | 10:00pm | In person | Advik Mehta (worked remotely) |
| Aryaman Raina |
- All user stories finished at this point
- Continued working on the UI tests for Part 4
- Addressed TA feedback from Part 3
- UML diagram
- Debugged outstanding issues