DTR_IntentionTimer

Group Member Names: Nicole, Katy, Orlando

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?):

Understanding how the data model and the DOM work together.
Get faster.
Better understanding of each iteration before moving on to the next one.
Refactor each iteration before going onto the next one.
Putting HTML, CSS, and JS together.


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

Orlando: Works well with driver-navigator.
Nicole: Also likes driver-navigator. Easy-going.
Katy: Laid back, patient.


How we can use our strengths to overcome obstacles:

Driver-navigator helps there be better communication throughout the project. Communication is key! 


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):

Nicole is available every evening from 7 pm to 10 pm and can be available sometime during Saturday and Sunday, will just need to schedule childcare accordingly. We won't work on the project on Sunday afternoon. We will do driver-navigator for 4 hours max on the weekdays and 6 hours max on the weekend days.


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?):

We will communicate on a daily basis with slack and use tuple for our driver-navigator calls. We will also exchange phone numbers.

We'll make decisions as a team by listening to each other and talking things through.

We will take poms and communicate about our need to take breaks. We will also check-in with each other at the beginning of our meetings.


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

Understanding how the DOM and data model work together.
Frequent commits, at least 100 commits.
Use a PR template.
Git workflow, one person working on one branch at a time.
HTML, CSS, and JS style and organization.


Workload Expectations (What features do we each want to work on?):

We'll each work a little bit on each iteration of the project. If there's a topic that someone is not understanding well, they will be the driver while working on that topic.


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

We'll each be doing an equal amount of commits and pull requests. We'll communicate through any merge conflicts by talking to each other but also in written communication so that it is documented and we'll resolve them through GitHub.


Expectations for giving and receiving feedback:

Be respectful to each other. Communicate especially if someone is not understanding something. It's good for us to practice giving and receiving feedback.


Additional Remote Considerations:

If we do not have good internet connection we can talk over the phone.


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

If we decide we want to use a project management tool, we will use Trello.