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?):
- Ruby would like to gain more experience with prototype array iteration methods. Kyle would like to practice testing with hooks and getting SRP code.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- We are both pretty well versed in HTML, CSS and JavaScript. We feel very comfortable with classes, testing, and functions. We have similar Pairin qualities. We're both imaginative-inspirational. Ruby is "reliant" while Kyle is a "loyalist." These two attributes are similar, so we will need to be more assertive in deciding what to do when working on projects.
How we can use our strengths to overcome obstacles:
- Since we tend to do our best work when we are being told what to do, we need to work on being more assertive with eachother. We're quite similar in our work ethic, so we need to change a bit in terms of how we delegate tasks and work together.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- Kyle sets aside 5pm-6pm every day to eat with his family. Ruby prefers not to work on Friday or Sunday nights. Communication past 7pm is not expected to be replied to until the following day.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- We'll be working on our own branches made from issues on the project board. Merging will always be done together.
Expectations for giving and receiving feedback:
- Try not to take things personally. Address the code and not the person. If you do have feedback, provide an alternative solution rather than keep the conversation all negative.