DTR

# 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 your learning goals for this project? What drives us in this project?
* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
* How do you communicate best? How do you appreciate receiving communication from others?
* How would you describe your work style?
* What are your strengths? How can our strengths complement each other?
* What’s gone well or poorly in your previous projects?
* How will we set direction and make decisions as a team?
* How will we overcome obstacles?
* What do you need (resources, environment, communication) to do your best work?
* What scheduling restraints do you have? What are your scheduling preferences?
* What is your style for giving feedback? Does anything ever hold you back from giving feedback?
* 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?
* What tools do you want to use to manage the project?
* How do you want the group to solve problems when members run into issues with features of the project?
* How do you know if a project is successful? How can we achieve that as a group?
* How will we recognize each other's successes and celebrate them?

Any additional questions that you would like to add:






### Template for DTR Memo

Project: ToDo box 

Group Member Names: Maria and Julie D. 

Project Expectations: What does each group member hope to get out of this project? 
Maria - learning to refactor and finding best practices from the last project. Improve selector capability. 
Julie - Wants to work on understanding the search function and understanding local storage. Also communication is kept up. 

Goals and expectations:

##Team strengths:
Maria - Stronger on CSS/HTML than javsScript
Julie - Stronger on CSS/HTML than javaScript


## How to overcome obstacles:

Talk through it. Seek help as often as possible. Pair often. 


## Schedule Expectations (When are we available to work together and individually?):

Sunday - get a good start on work. Stay after class for an hour and a half and then work from home at night usually after 8 p.m. 

## Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):
 
We communicate often - telling eachother what we are working on and ensuring we don't overwrite. 

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


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


## Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): 
We branch everything - we talk before pushing to master. Put in pull requests when we're ready for new pieces. Console log everything as we go. 

## Expectations for giving and receiving feedback:

Make sure we explain our thought process and ask questions from each other. Do it kindly and with respect. 


Agenda to discuss project launch:
Step 1 - get it working
Step 2 - refactor
Step 3 - New functionality



Ideas:
 
Tools: 

Additional Notes: