MeganHuggins · February 3, 2020 19:55
diff --git a/DTR: Define the Relationship b/DTR: Define the Relationship
 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?
 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 each of our 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:

 Group Member Names: Megan Huggins & David Pernitz

 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?):
 We both want to learn to relinquish certain amounts of 'power' one has over the project as a whole (aka not feeling like we have to do everything ourselves for a good end result). We want to achive a solid, complete project as well as learn together. 
 Team strengths & collaboration styles (consider discussing your Pairin qualities here):

 How we can use our strengths to overcome obstacles:
 We are both hard working and good at problem solving, whether that be from googling or code pen. By allowing us to switch/ teach our individual ways of problem solving we look forward to adding new strengths. 

 Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
 We both have availbilty to stay after class (within reason and schedules) and are both okay if sometimes this changes. Also, can both make saturdays work for coming into Turing. We both would like to keep weekend work to Saturdays only and sundays mainly free.

 Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
 We plain on commincating/ touching base daily (with the exception of sunday) and will prioritze meeting in person but slack can and will be implmented as well. Decision making will be understood through the mantra of "don't be dick."
 Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
 We both hope to strenghten our CSS sicks as well as coming at problems in a more thought out way (aka dont make it harder than it needs to be)

 Workload Expectations (What features do we each want to work on?):
 Workload will be even and not used as a cruch if understanding is lacking in a certain area.  We are also, going to work on not doing everything our ownselves,  instead being better delegating.

 Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
 Making sure to have good and easy understandable naming to git pushes and if any confusion ask and relay what was changes and why. Using trelo to keep track of todo tasks as well a using slack call to pair remotely

 Expectations for giving and receiving feedback:
 again, dont be a dick. Come to eachother with understanding and empathy and work together to an end goal instead of working against eachother.

 Project management tools we will use (GitHub projects or Trello are popular tools):
 Trelo will be our main project management tool as well as slack check ins and information log. 

 Day 1 Agenda:

 Additional Notes:
	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?
	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 each of our 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:

	Group Member Names: Megan Huggins & David Pernitz

	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?):
	We both want to learn to relinquish certain amounts of 'power' one has over the project as a whole (aka not feeling like we have to do everything ourselves for a good end result). We want to achive a solid, complete project as well as learn together.
	Team strengths & collaboration styles (consider discussing your Pairin qualities here):

	How we can use our strengths to overcome obstacles:
	We are both hard working and good at problem solving, whether that be from googling or code pen. By allowing us to switch/ teach our individual ways of problem solving we look forward to adding new strengths.

	Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
	We both have availbilty to stay after class (within reason and schedules) and are both okay if sometimes this changes. Also, can both make saturdays work for coming into Turing. We both would like to keep weekend work to Saturdays only and sundays mainly free.

	Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
	We plain on commincating/ touching base daily (with the exception of sunday) and will prioritze meeting in person but slack can and will be implmented as well. Decision making will be understood through the mantra of "don't be dick."
	Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
	We both hope to strenghten our CSS sicks as well as coming at problems in a more thought out way (aka dont make it harder than it needs to be)

	Workload Expectations (What features do we each want to work on?):
	Workload will be even and not used as a cruch if understanding is lacking in a certain area. We are also, going to work on not doing everything our ownselves, instead being better delegating.

	Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
	Making sure to have good and easy understandable naming to git pushes and if any confusion ask and relay what was changes and why. Using trelo to keep track of todo tasks as well a using slack call to pair remotely

	Expectations for giving and receiving feedback:
	again, dont be a dick. Come to eachother with understanding and empathy and work together to an end goal instead of working against eachother.

	Project management tools we will use (GitHub projects or Trello are popular tools):
	Trelo will be our main project management tool as well as slack check ins and information log.

	Day 1 Agenda:

	Additional Notes:
No results found