Product Owner Meeting Notes - acarso02/3760_Checkers GitHub Wiki

6/10/21

  • user stories are too broad

  • break large components into smaller parts

  • eg movement into: select piece, check for legal moves, display moves

  • main gameplay is too large for the time, since it needs to be fully implemented and tested each sprint

  • What should we start with?

  • Product Owner (prof) advised developing UI over developing game since the associated stories are easier to manage

  • Any recommendations for documentation?

  • written in a document? wiki’d?

  • specifically our internal documentation (what do we document?)

  • user story stuff

  • PO: It should be done in a sane way, Git is a good option, use some kind of Kanban board

13/10/21

*can all our notes/design stuff/trello/etc be reached from one place?

  • no, we need to fix that

  • formalize testing

  • testing process

  • evidence it was followed

  • We can use time stamps to show when a test was assigned, done

  • screenshots or video of the test being done also works

  • Deadline extended

20/10/21

  • There is space for additional user stories

  • Piece capture is a good target/story

  • Split multicapture, single capture into two stories

  • Concerning "verify legal moves"

  • Showing all legal moves removes some skill

  • Could be good as an optional setting (this should be a push goal)

  • Verifying legal moves is necessary though

  • If we need to drop anything, drop the king piece thing

  • If you have a short implementable feature, that isn't tracked, does implementing break agile

  • It depends, does it break other things? Or is the risk of breaking of it small?

  • You need to track the changes no matter what

27/10/21

  • Link user stories with task
  • Add user stories to github and then make subtasks

  • See if you can add user stories to project board and then divide into subtasks

  • Add name of user stories and sub-tasks to project sprint items

  • Animation not necessary for milestone 2
  • Dont need pause menu for alpha (milestone 2)
  • Need to be able to move legally
  • Need to be able to jump
  • Add user story information into tasks descriptions
  • You can break being able to jump as a piece into two user stories

  • As a user, I would like to be able to capture a piece

  • As a user, I would like to be able to capture multiple pieces

  • Milestone 2 and 3 deadlines due friday night but you can have 48 hour grace period to submit. Same as milestone 1

10/11/21

  • Clean backlog
  • Goals should be

  • First finish basic loop

  • Second do as much polish as possible

  • Do a test build sooner rather than later

17/11/21

  • polish is not strongly graded, but matters
  • Integrate linter and document it
  • Having multiple scenes for test configurations will save time

24/11/21

  • We are basically on track! To Review list is a little excessive but still
  • Keep tracking simple
  • Strongly need to test build

  • Do this while doing our testing for user stories

  • Stat tracking should have some default names or previous names for convenience