- Group Member Names: Taras Tarlov, Trond Makonese
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?):
-
Better understanding of react, router, nested api fetch calls
-
Gain as mush knowledge as possible from team member, able to break down a difficult concept with great articulation.
-
Hitting our mvp, hopefully get an extension completed. Deep uderstanding of the code base.
-
Pairing is impoirtant, would like to tackle more difficult concepts together.
-
strength: Feels relatively comfortable with react as this point.
-
Same as Taras
-
strength: reaching out for help when needed, good amount of knowledge with the material
-
When stuck reach out!
-
lean on eachother for support!
-
Take palms!
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
-
If ahead of schedule, take a self day during the weekend.
-
During school work time we will pair, if needed we will work longer hours
-
Quite time after 9:30 pm
-
Weekend: Saturady meet at noon, Plan Sunday to be the day off depending on how much work has been completed
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
- Slack, quite time after 9:30 pm
-
Testing!!!
-
Growth in all areas required for the project such as react, router, componentDidMount ect.
- 50/50
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
-
Alot of paired programming, will have smaller task to complete outside of pair work such as styling and basic testing.
-
Trello
-
Code Reviews before merging to master
- Keep communication open and honest. Nothing is a personal attack.
- Trello