Skip to content

02 25 21 sprint 2 halfwaypt

luluzhu9 edited this page Feb 26, 2021 · 2 revisions

Sprint #2 Halfway Point

Team: Powell's Owls | Group 33

Overview

Date Time Type of Meeting Where
02/25/2021 6pm PST Feedback & Planning Zoom

Key Points

  • Feedback from team:
    • Pair programming vs. solo programming, may go back to Pair programming
    • Office hours valuable
  • Make sure you update your branch if you have a new branch to keep it up to date
  • Make sure style is correct: function headers (especially param) and comments
    • "this": do not use often because it's not how we should use scope , only use for things control needs to access, everything else lives in constructor
      • Eg: use const instead
    • Lambda function: anything control needs to access, must be Lambda
      • Use normal functions for any function greater than 3 lines
  • PR:
    • Requires a few unit tests
    • Line by line comments
    • Add tags of status
    • Add projects so that the backlog is done manually
  • Create separate component for reused components like buttons especially; will do during sprint 3
  • This weekend: start incorporating toggle to side bar
  • Powell said check-in rate needs to be okay
    • Update issues, make comments to changes you make, update backlog, have lots of commits
    • Will affect everyone's grade
    • Check in everyday! A small comment that you didn't do anything today is absolutely fine
    • Delete stale branches (not agile)
  • Work distribution
    • Do more ADR, documentation, and unit/manual testing if you're doing less work in code
    • We're behind on testing
  • Make issues more specific to update expectations
  • Features
    • Refinement:
      • Example: hovering over button makes it highlighted
      • How the sidebar slides out
      • For finish: does it drop down, make it more engaging
    • Separate branch for sidebar testing, integrate audio well, toggle switches, tab notifications
    • For first time users (IP address) get told why things are grayed out
    • Stats: think about what you're interested in even if its not your task
      • Donut style
    • Sidebar and Info: dim rest of screen
      • Vy will implement it in info and others can copy and past it
    • Testing: if you haven't done lab yet, do manual testing
  • Design questions
    • Rename Finish button to Stats, still thinking about having it either below start or the bottom right
      • Finish button not responsive when window resizes
      • Minimum width is size of sidebar
    • Break color: have multiple colors

Attendance

  • Michael Donaldson
  • Richard Duong
  • Brandon Liu
  • Bryant Shao
  • Steven Steiner
  • Nicole Trappe
  • Vy Truong
  • Felix Zhang
  • Lulu Zhu
Clone this wiki locally