aGroup Member Names: Andy Tom and Justin Volk
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?):
Andy: I'd like to work more on testing for sad paths.
Justin: Get better with testing, have a better understanding of what each test is doing.
Both: Get back to DOM manipulation. We'll know if we can explain our code to someone else and have good workflow. We want ideally complete 4 iterations but if we don't, as long as we learned as much as we could. We want a working application with as little bugs as possible.
How we can use our strengths to overcome obstacles: We are different in a lot of ways, Justin can bring in the imaginitive part and Andy will be the objective-analytical part. Justin will bring the energy and enthusiasm and Andy will help carry this through to the end. We both want to work hard.
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 a break between 4-5. Andy likes to get done before 8. Justin has not many scheduling constraints. I also like to take a break after 4.
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?):
Communicate every day, use slacks built in messaging. Doesn't have to be big messages, keep most commuunication to verbal, easier to understand tone.
Andy: Improve understanding of grid and css. Get a better understanding of TDD.
Justin: TDD and better Dom interactions.
Workload Expectations (What features do we each want to work on?):
Andy: Css and grid html setup
Justin: If we do driver-navigator we'll all end up knowing how to do everything.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
Use the PR template, if we do work separately, using annotations when merging a pr for better understanding.
Try not to work too much, after 40 minutes try to take a break if necessary.
Constructive, try to give it verbally if possible.
We've been remote for a while now, we are getting into it.
Trello
Finish DTR, Set up project board, Potentially start 1st iteration Additional Notes: