Group Member Names:
Fenton Taylor
Mack Halliday
Zoe Ketcham-Harvey
Mike Schnieder
Quinne Farenwald
Goals and Expectations for the Project:
Create a tight MVP and kick ass
Learn new frameworks/languages, FE: React Native, BE: Python & Jango
Demo comp!!!
Team strengths & collaboration styles: Fenton: group expert
Quinne and Mike: design backgrounds
Zoe: Experience with React Native
Mack: Documentation and workflow
Over communication
Expectations often and early
Daily stand ups to kick off and wrap up the day
Anything code related, goes in GH project board
Anything social/team related, goes on Slack
How we can use our strengths to overcome obstacles:
Communication
No freaking out when stuff breaks, calm down and we will all work through it
Schedule Expectations:
Zoe: Super flexible during school b/c lives close by, wants to get out of the basement to work. Night owl, nothing too early. Out of town all of break.
Mike: If critical work likes to stick around after school, second wind after dinner, wrap it up at night. Weekends, sleep in, happy to work where ever. No travel plans for holiday, maybe gone for 3 or 4 days and can work a little.
Quinne: Turing is my life. Early morning and night owl. No holiday plans. Like to get out of basement. 10pm cut off.
Mack: Gone 24 - 29th for holiday. Ok to work over break. Night owl. Live close to Turing.
Fenton: During week, leave here by 5pm, then work after dinner till about 10pm. Weekends, half day of dont touch the computer/light coding and other day go hard. No travel plans for holiday and working over holiday.
Communication Expectations:
Never annoyed with too much communication
If messages come in late, no need to respond that night
Other expectations listed in topics above
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
Learn new frameworks/languages, FE: React Native, BE: Python & Jango
Really polished project
Bugless app
Learn to communicate with people from The Other Side
Workload Expectations:
If/when people travel, no expectations of work required.
Workflow Expectations:
Numbered user stories - user story was name of PR
Descriptive commit messages
PR template
PR tie back in with issue number
We will follow back end team's examples of this...
Separate branches (master is ONLY for perfect code)
Expectations for giving and receiving feedback:
Be polite and honest
"There is a problem"... not any one person is the cause
Project management tools we will use (GitHub projects or Trello are popular tools):
GitHub Projects
Day 1 Agenda:
DTR
Weekend plans for researching and setting up user stories