Meeting Minutes

Wednesday, January 21 - TA Meeting

Attendance - Everyone was present for the client meeting!
Agenda - get to know the client’s needs, how the game works, and if we can brainstorm some more ideas to be creative.

  • We will have a weekly recurring meeting with the Client on every Wednesday at 9:45am
  • Get familiar with the software framework/engine in Unity.
  • Map out the components of the system we want to build (how backend and frontend communicate with each other).
  • Major data elements - the backend stuffs that we need to track for our project (can be a UML class diagram).
  • Interaction scenarios - sequence diagrams to show how our system works, how the code is called, and how it returns through our system. (how the components of the system interact with each other)
  • Create a mock UI on how the application will look and how the users will interact with it (mark the user stories also that are filled). Make it minimal.
  • Project management: Storymap: with all user stories and at what stage we wanna complete them.
  • Once we have all user stories then group them by must have, should have etc, ask the client about the priorities. Do higher priority stuff for sprint 3 and 4.
  • All meetings should have meeting minutes! (agenda, attendance).

Wednesday, January 21 - Client Meeting

  • The map.
  • Start the game on START.
  • Show the characters for children, start rolling the dice.
  • In grey spot, grab a pom pom and put in cup.
  • In blue colour, they will choose the card from the deck- it can be fact or question.
  • If the question was answered, they will remove one of the air pollution from the cup, and if it's wrong nothing will happen.
  • If it was a fact, it won't matter.
  • In green spots, do diff activities- ride a bike, use public transport etc...
  • We can also show a cool fact on the green spots.
  • It can potentially tell how many plants to grow as well.
  • At the end count the air pollution, and based on the AQHI map we see the air pollution.
  • Optional requirements- multiplayer (3) games - like a kahoot game (‘code’) - important.
  • Multiplayer- teacher (admin?) view/ student player view
  • Question: multiple choice options.
  • Facts - clickable option - ‘cool’ ‘fun!’.
  • UI Map should look like a given - zoom as you play (3D? - aerial view - optional).
  • CANVAS CAN BE FLAT BUT STRUCTURES CAN BE 3D.
  • Sketchfab / blender.
  • We can put in our ideasss!!
  • Landscape game cause chromebook (Not a touch screen game, with a keyboard and mouse/touchpad).
  • Different tiers in the game (easy, medium, hard).
  • Potentially 3 kids on a team, where a team of 3 acts like a single player.
  • For younger kids, roll the dice and move through the map (fact cards only for the younger kids) -> minimal cards with easy facts, minimum texts, and also more images to make it interesting.
  • For older kids, have harder questions and facts.
  • Can have a read-aloud feature to read it out for the younger kids.
  • Speaker option for younger kids, light/dark mode, text size adjustments.
  • Can get facts from the client itself!
  • We can also update facts with time.
  • (Not a requirement) Kids can also make their own facts (nice to have but not a requirement) -> look into it later, not high priority.
  • Images of characters + asset library (FOLLOW UP).
  • Asset libs can help w 3D stuffs (maybe, iffy).
  • Make the text a little bigger if it's smaller for kids.
  • Instead of having a pom pom ball for air pollution, we can actually have a lung/cloud that keeps getting darker or more intense as the pollution increases.
  • We can add a coughing sound effect if they land on a place with a high pollution level. (we can ofc turn it off).
  • Can have background music but need the option to turn it off too.
  • Maybe we can use diff sounds/music for diff places on the map.
  • Maybe we can later make it a little harder (after trial and error) if the kids just seem to keep scoring all the time and don't really get to learn.
  • When you get a question wrong, you move back a spot.

Friday, January 23 - Team Meeting

Attendance - All team members present!
Agenda - Plan and do considerable work for sprint 1

Actions:

  • Built team canvas on Figma
  • Team roles filled out

Everything needed for sprint 1 was assigned except for:

  • Major data elements
  • Project management (Storymap and Project backlog)

We need to wait on more specifics about multiplayer in order to create those documents.

Decisions Made:

  • Sridhar will be scrum master for sprint 2

Before January 28th 2026 at 9:45 am:

  • Get everyone access to the github
  • Complete individual tasks
  • Every person creates the acceptance tests for 6 user stories.

Individual Tasks:

  • Pouyan - Low-fidelity user interface (UI flow diagrams)
  • Vikasini - Write the project overview (summary), glossary, check-out the user stories
  • Ben - Create sequence diagram for game with no server (for now), Technical resources, Detailed list of technologies
  • Eric will write / draw the High-level software design document + Similar / open source Products
  • Maansi - User story acceptances, User stories
  • Sridhar - User Story Acceptance Tests, Start working on the Markdown Documentation
  • Ipsa - UML class diagrams

Agenda for next meeting:

  • Make updates for multiplayer decision
  • Create github docs

Wednesday, January 28 - TA Meeting

Attendance - Everyone present

  • Discussed with the TA on what each team member is gonna do this week (and what they have done in the last week).
  • Discussed on what happened in last week’s client meeting
  • Suggestion from TA: Don't go for multiplayer features (can add more work which might not be feasible in just 1 sem).
  • SPRINT 1 DEADLINE - FEB 1 (SUNDAY)
  • Separate user stories for admin

Wednesday, January 28 - Client Meeting

  • Local Multiplayer: first in mind, with a framework for network multiplayer for future development down the line
  • Confirm playing with bots for singleplayer
  • New assets will be added to folder
  • Minigames: not completed all of the ideas, can have more, has only included 2 ish for now, can develop more later
  • Multiplayer depends on time
  • Minigames triggered in multiple spots
  • All other meetings 9:45 am
  • Leaderboards: fun to have, maybe resets once per day, how to juggle multiple classrooms playing – nice to- have
  • Possibly stored locally, have to figure out way to filter inappropriate names
  • Multiple classrooms may be accessing site at same time will send Discord link to clients
  • Okay rebuilding editing text feature through Unity

Wednesday, January 28 - Team Meeting

  • Finalize individual tasks
  • Fix user stories/acceptance tests
  • Make issues and assign US in Github Board
  • Likely meet Friday nights weekly
  • Create US for leaderboard
  • Completed a portion of Story Points together
  • Players cannot create facts anymore, we’ve decided
  • AD.03 cut
  • Make explicit stories for each character and their abilities
  • Send clients the discord link
  • Add user stories for bots
  • Considering question variety, such as matching type questions
    • Add this as user story

Friday, January 30 - Team Meeting

Attendance - Everyone but Maansi

Done at meeting:

  • Created story map
  • Made github issues for all tasks due by the end of sprint 1

Due by Sunday at 11:00am:

  • Everyone finishes their GitHub issues assigned to them.

Sunday, February 1 - Team meeting

Attendance - Everyone

Done at meeting:

  • Divided up remaining tasks for sprint 1.
  • Moved ABE.09 and ABE.10 to Sprint 3, MM.02 and MM.04 to Sprint 2, GBM.12 to Sprint 4
  • Moved ACC.01, MG.01, MM.02 and MM.04 to Sprint 2, ABE.09 and ABE.10 to Sprint 3, GBM.12 to Sprint 4
  • Assigned each team member user stories for sprint 2.

Due by tonight at 7:00pm:

  • Finish up all sprint 1 items.
  • Sridhar to make the GitHub release.

Wednesday, February 11 - TA Meeting

Attendance - Everyone

  • Work on the high-level architecture diagram
  • Have more open-source products, there should be more research
  • Have a link of the similar products, and how we can be using it
  • Inconsistencies with the user stories
  • Inconsistencies and issues with some acceptance tests
  • Work on some of the admin user stories
  • Marks will be uploaded soon
  • Have a clear strategy for testing
  • Testing is important (try for each user story as you are doing them)
  • Write unit and UI tests consistently
  • Document if your user story is completing specific unit tests
  • Potentially have 1 unit test per acceptance test

Wednesday, February 11 - Client Meeting

Attendance - Everyone

  • Demoed the game
  • Asked for 16:9 map
  • Asked for detailed explanations on blue cards
  • Boss Battle clarification
  • Moving Backwards for wrong answer clarified

Wednesday, February 11 - Team Meeting

Attendance - Everyone

  • Fixed Git Branches
  • Decided on tasks till release
  • Meeting on friday night and sunday morning

Friday, Febraury 13 - Team Meeting

Attendance - Everyone

  • Everyone has individual tasks to do, mostly testing
  • We will meet again Sunday morning to finalize things for the sprint
  • If anything bad comes up we will meet Saturday

Sunday, February 15 - Team Meeting (Last day of sprint, 12:30pm)

Attendance - Everyone

Final individual tasks assigned:

Code to be pushed before 2:00pm:

  • Sridhar: Tests
  • Vikasini: Final Score + Tests
  • Pouyan: Fix Settings Menu + Tests
  • Maansi: Tests

Tasks before final merge:

  • Sridhar: Sheets Update + MG US + Final Commit + Release
  • Vikasini: Sheets Update + Tasks + MG US + GH Issue Acceptance Tests
  • Ben: UML + MG US + New Story Map + GitHub Issues
  • Eric: Sheets Update + Tasks + MG US
  • Ipsa: Sheets Update + Tasks
  • Pouyan: Sheets Update + Tasks + MG US
  • Maansi: Sheets Update + Tasks + MG US

Tuesday Feb 17 - Client meeting

Attendance - Everyone - For multiplayer, max of 3 players, if two players want to play as the same character the cape colour will be assigned randomly to indicate that the two characters are different. - Clients will give us images for questions and questions in mcq form and explanation messages for when the player gets it wrong or right - Clients will give us 16:9 aspect ratio of game board - Clients will give us different versions of the character art with different cape colours - Assets will be given in the next 2 to 3 weeks - Next meeting will be on the 24th at 1:30pm

Tuesday Feb 24 - Client Meeting

Attendance - Ben, Ipsa, Maansi, both clients

Very short meeting

Clients may add a few squares to the board when making it 16:9 in order to fill empty spaces. No new space types will be added, just more of existing types.

Wednesday March 4 TA Meeting

Attendance: Everyone

Told that we need to add tasks for sprint 4 during sprint 3.

Wednesday March 4 Client Meeting

Attendance: Everyone except Maansi

Demoed new UI changes to clients.

Clarified that bosses would appear at the end of the game.

Wednesday March 4 Team Meeting

Attendance: Everyone except Maansi

Decided that Pouyan and Vikasini will do UI/UX/Accessibility requirements for sprint 3.

Decided that Ben will do automated testing for sprint 3

Friday March 6 Team Meeting

Attendance: Everyone

Things to do before Sunday morning - Everyone: Make tasks for there user stories (Both sprint 3 and 4) - Everyone: Finish user stories - Ben: Finish fixing tests so that all run on github actions - Pouyan and Vikasini: UI/UX/accessibility items - Pouyan: Large text toggle

Meet next at noon on Sunday the 8th of March

Sunday March 8 Team Meeting

Attendance: Everyone

Things to do before 6:00pm: - Vikasini: Tasks for sprint 3 and 4, Requirements Traceability Matrix, last acceptance tests - Pouyan: Tasks for sprint 3 and 4, Large text fix, Requirements Traceability Matrix - Maansi: Requirements Traceability Matrix - Ipsa: Requirements Traceability Matrix - Eric: Tasks for sprint 3 and 4, Testing Matrix, reorganize test - Sridhar: Requirements Traceability Matrix

Merge to main and create release

Wednesday March 18 TA Meeting

Attendance: Ben, Eric, Pouyan, Maansi, Ipsa

TA's Feedback on sprint3: - Missing product owner for sprint3 and 4 - UI heuristics should be in the REPO - testing matrix in the repo - Fix overlapping text in large text mode - Pause button always available - Big text mode does not work on final score screen - Deploy to itch.io

March 18, 2026 Client Meeting

Attendance: Ben, Eric, Pouyan, Maansi, Ipsa Client Feedback: - Check Colour blind colours - Real dice - Move dice to left - Swap map - Air pollution information - Images for cards by next friday - Make the box smaller if there is no image - Make the character info more clear that you can click it - Read aloud on question feedback screen - Boss screen should not have submit button on questions - End game screen -> Play again button - "Great job you helped clean the air" message - "Credits screen" - How to play screen before you open the game - "Learn how to play" or "Play the game" - Make "Click on character to know more" more clear - Put box around the ability on the character select screen to show that it is a button - Pictures of trees in tree minigame - Make background brown in three minigame (soil) - Send screenshot of mask minigame to Charlee to ask artist to make new assets - The boss questions should not be visible before hand at all - Character goes next to the podium to finish - Flat colour around 3d map - no bottle caps on 3d map - BIllboards are prefered for mountains on 3d map

March 22 2026

Attendence: Everyone

Vikasini: Acceptance tests Everyone: Merging PRs Sridhar: Fixing multiplayer test case Add testing matrix and UI info to docs Add to testing matrix: Eric, Pouyan, Vikasini

Merge sprint4 into main at 6pm

March 25, 2026, TA Meeting

Attendence: Everyone, but Pouyan

  • Client and user instructions manuals (PDFs in the repo)
  • We don't actually have to deploy for client
  • Job description needed to work on project (PDF in repo, in the root)
  • CMPUT 401 portal, log in to the portal with ccid
  • Screen cast, not part of the sprint, for future employer
  • 3D tests can be done manually, and noted in the repo

March 25, 2026, Client Meeting

Attendence: Everyone, but Pouyan

  • Next meeting: Monday at 9am
  • Clouds go from white to pollution filled from the left to the right of the map
  • Focus more on polishing then features
  • Remove bears
  • Add back cows
  • No retry button on minigames
  • Repeat existing minigames on 3 blank green squares