ParingDTR

# DTR: Define the Relationship

Use this template to when conducting DTR with your project partners. *It's recommended that you copy/paste this template into your own gist each time you conduct a DTR to take notes on the conversation.* 

### Guiding Questions to Define The Relationship:

* What are each of our learning goals for this project? What drives us in this project? - D: Good understanding the routing of user information. J: Stronger understanding of vanilla JS.
* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? D: Pair programming. J: Pair programming.
* How do you communicate best? How do you appreciate receiving communication from others? D: Openly, frequently, and honestly. J: Openly, frequently, and honestly.
* How would you describe your work style? D: Longer bursts of creatvity, then break. J; Work for 2-3 hours, break, work again.
* What are each of our strengths? How can our strengths complement each other? D: Conceptualization. J: Quick learner.
* What’s gone well or poorly in your previous projects? D: Poorly: responsiveness. Well: Positioning. J: Poorly: responsiveness. Well: HTML/CSS syntax.
* How will we set direction and make decisions as a team? - Aim towards a finished product, while speaking openly and gently.
* How will we overcome obstacles? - Communication, breaking down problems.
* What do you need (resources, environment, communication) to do your best work? - Time, resources, motivation.
* What scheduling restraints do you have? What are your scheduling preferences? - Wed at 7: bad. Mon-Sun 10pm-6am: bad.
* What is your style for giving feedback? Does anything ever hold you back from giving feedback? - Open and honest.
* What do you identify as being your biggest strength(s) technically, as they relate to this project? Where do you feel you could use improvement in your technical skills, as they relate to this project? How can our team help support you in improving these skills? - Positioning and clean HTML are solid. Need imporovement on JS and some CSS aspects. Support will come in the form of encouragement.
* What tools do you want to use to manage the project? - GitHub.
* How do you want the group to solve problems when members run into issues with features of the project? - Brainstroming and communication.
* How do you know if a project is successful? How can we achieve that as a group? - It will function as needed.
* How will we recognize each other's successes and celebrate them? - Alcohol and high fives.

Any additional questions that you would like to add:






### Template for DTR Memo

Project: Number Guesser.

Group Member Names: Jev Forsberg, David Engel

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?): Finish on time. Produce useable game. Feel strong about features.
	
Team strengths & collaboration styles (consider discussing your Pairin qualities here): Creatvity and inginuity; pair programming.

How we can use our strengths to overcome obstacles: Reducing problems to smaller, achievable steps.

Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Wed at 7: bad. Mon-Sun 10pm-6am: bad.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): Chat everyday, work before and after class.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Good understanding the routing of user information. Stronger understanding of vanilla JS.

Workload Expectations (What features do we each want to work on?): Don't want to break up work before we know more about the project.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Do all of the above.

Expectations for giving and receiving feedback: Open, honest, frequesnt, empathetic dialogue.

Project management tools we will use: GitHub, Slack calls, calendar.

Day 1 Agenda: Bang out HTML structure.

Additional Notes:

I appreciate how thorough you got with your responses here!