Group Member Names: Danny Ramos, Derek Borski, Jack Gould, John Watterson, Andy Tom

Goals and Expectations for the Project (What does each group member hope to get out of this project? What do we want to achieve as a team? How will we know that we’re successful?):

Get a full understanding of front end and back end, how they are married. Understand Redux. Lean into the code annotation, spend time getting an understanding of how the data flows.

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

Driver navigator when possible. Pair front end and back end and annotate together. Utilize the github project board.

Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):

Take an extended break around 4. Don't have calls scheduled after 8. Be flexible with interviews/schedule conflict. Take friday nights off.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):

Make a dedicated slack channel with instructors/project managers. Over communication, especially over calls and pairing. Jump on a call for quick questions if possible. Daily standup at 1pm.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement):

Getting a better understanding of the area you are not familiar with, front end or back end. Write and speak technically when expanding on ideas and presenting. Learn how to learn a new language on a brand new codebase. Leaving enough time and space for everyone to learn what they want. Spend time researching new technologies before coming together to pool resources.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

Git Rebasing Miro - wireframes, data flow Problem-solving techniques: Ask questions after being stuck for a bit. Post on slack when you have a PR open, try to comment in the PR what the code does. PR template. 2 person minimum, front end back end.

Pomodoro Break Schedule:

30 mins on, 7 mins off. After 2 or so hours, take a longer break.

Expectations for giving and receiving feedback:

Be straightforward and sincere. Don't be shy, constructive feedback is welcomed. Formulate some feedback for eachother throughout the project, wins and specific feedback.

Additional Remote Considerations:

Project management tools we will use (GitHub projects or Trello are popular tools):

Github Projects

Day 1 Agenda:

DTR, create channel, try to get project running, create project board.