Project: RomCom
Group Member Names: Derek Romero, Nick Hart
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?):
Derek - Closing in on some of the gaps with functionality of js. Nick - Just wanting to jump in head first. Honestly, I have no idea what to expect here.
Learning to work as a team within the development environment. We both want to use this as an opportunity to grow. At the moment, it's hard to articulate exactly what we'll be looking for to know we're successful. We want to see growth as teammates and developers.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
We both want to work together to make this happen in the best way possible. We're both strong facilitators and task oriented people, so we'll use the iterations and rubric to our advantage.
How we can use our strengths to overcome obstacles:
Again, we're both team and task oriented, so we expect when obstacles arise we'd confront them directly and work through them together.
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):
MWF: 7 - 10, TTH: flexible, Weekends: pretty flexible
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?):
Communicating through slack and zoom, pretty regularly. Feedback is important to both of us, and we're both gonna be pretty open about how we feel about things.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
A big goal is understanding the macro viewpoint of how things work together between js, html and css. If we come out of this feeling comfortable with meeting the technical expectations laid out on the rubric, we'd consider that a win. Being able to explain all code is a huge goal, as well.
Workload Expectations (What features do we each want to work on?):
Striving to hit at least 80% work as driver navigator will be a good way to split up the work. We'll let the driver navigator workflow dictate how we move forward splitting up features.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
Starting with pseudocoding, working together to make features, small commits and thorough code review with PRs. Really working to ensure even split between pushing code up and reviewing it.
Pomodoro Break Schedule:
The frequency may vary a little day to day, but depending on the day we'll decide on the intervals and stick to them.
Expectations for giving and receiving feedback:
We're both pretty open about giving and recieving feedback, and we'll be proactive about it for our own sakes.
Additional Remote Considerations:
No real logistical considerations other than the scheduling ones, which have been discussed earlier. Communication wise is the same as above.
Project management tools we will use (GitHub projects or Trello are popular tools):
We'll use Github projects as well as Tuple.
Day 1 Agenda: 7 to 10 pm. Nick will have Tuple set up. Goal will be to tackle iteration 1.
Additional Notes: Thursday we will plan on revisiting this document to add/make changes as we learn.