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:

Martha Troubh & Martin Mercer

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

Our success will be shown in the quality and content of our commits and branches, that they represent our awareness and intentional work on specific functionalities. We will find success in testing through verifying before committing that we have tests for all testable methods. That also refelcts our understanding of the big picture, hitting on our desire to better understand algorithmic thinking and class interaction.

Team strengths & collaboration styles (consider discussing your Pairin qualities here):
Strengths: communication, seen the project before. Martha is a strong listener who is task oriented, interested in the details of a project. Martin is relationship oriented and someone who looks to the big picture, understanding it is made of small parts. Collaboratively, we both believe in strong communication and the idea that we will not move forward on the project without our partner--the major goal of this project ultimately is to be a good pair and learn together how to create a battleship game, rather than individually achieveing anything.

How we can use our strengths to overcome obstacles:

Being aware that there will be obstacles, and voicing our concerns as they arise. Focusing on the smaller tasks at hand and how they connect with the big picture

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

Our hard and fast rule are that we don't stay past 8pm. No constraints aside from Wednesday night. Otherwise, we're flexible for the duration of the project.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

SLACK! We'll communicate daily, though we'll probably be pairing together quite often. We will either talk about doing the thing before we do it, or we will present ideas having individually thought about it and come to a compromise.

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

See previous--we've covered it above, though our desired improvements have to do with Git workflow and algorithmic practices.

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

We're unsure of how we're going to break this, but we will revisit this question in the future. Ultimately, because of the pairing and the time-frame, it seems like it would be better to take this piece by piece.

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

We will have a branch for each major piece of functionality, and we will be be committing after each major change to a piece of functionality. We will ideally commit specifically after each test is written, and again after each corresponding piece of code. We will be working on a templates for our pull requests and commit comments, ideally focused on functionality (ex. "What does this PR do?" or "adds initialize method to ship class").

Expectations for giving and receiving feedback:

Open, honest, often. We want open and honest feedback, and would prefer no-holds-bar style where we try to help each other understand where we are with the project at all times.

Project management tools we will use:

Slack, atom, github, potentially github project thing but we don't really like it or care

Day 1 Agenda:

go over the entire project and psuedo-code at least the first iteration so we have a good starting point.

Additional Notes: