Palette Picker 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.* 


## Palette Picker

## Oct 7-17

### Guiding Questions to Define The Relationship:

* What are each of our learning goals for this project? What drives us in this project? 

B: Cleaner React Code, Fluency in Server-side.

G: Emphasis on Server/Backend. Refocus on FE Testing. 

* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?

B: Clear plan overrules all. 

G: Together to start, but always a stand-up/stand-down meeting.

* How do you communicate best? How do you appreciate receiving communication from others?

B: Slack messaging. Including Slack Chats. 

G: Slack massaging.

* How would you describe your work style?

B: Long-stretches of work time. With longer poms. 

G: Feels the same way, but when we are stuck on one thing for more than 30 minutes, I take a lap. 

* What are each of our strengths? How can our strengths complement each other?

B: Enjoys design. Comfortable with testing in general. 

G: Putting in hours. Might be ok to work with.  

* What’s gone well or poorly in your previous projects?

B: Everything's been great. 

G: Lack of communication. 

* How will we set direction and make decisions as a team?

B: Frontload planning. 

G: Stand-up and stand-downs to elaborate on what was accomplished and what to focus on.

* How will we overcome obstacles?

B: Talk about them early. Frame them according to goals of the project. Timeboxing appropriately.

G: Talk about what to expect from the code we write and work together. 

* What do you need (resources, environment, communication) to do your best work?

B: Sleep. Quiet Space. 

G: Communication. 

* What scheduling restraints do you have? What are your scheduling preferences?

B: Saturday Night.. Tuesday Night

G: Nothing as of yet. 

* What is your style for giving feedback? Does anything ever hold you back from giving feedback?

B: Ask for opinions. 

G: I want the best me. I need all critiques.

* What tools do you want to use to manage the project?

Clubhouse, Github Issues

* How do you want the group to solve problems when members run into issues with features of the project?

Alert them to the problems that they are facing. Timebox. And Then reach for outside help.

* How do you know if a project is successful? How can we achieve that as a group?

We will know this when we achieve the aformentioned learning goals. 
The goal is 3's and 4's. 

* How will we recognize each other's successes and celebrate them?

High fives. "You-did-it"







### Template for DTR Memo

Project: 

Group Member Names:

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?):
	
Team strengths & collaboration styles (consider discussing your Pairin qualities here):

How we can use our strengths to overcome obstacles:

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

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

Abilities & Growth 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/Debugging and Problem-solving Techniques): 

Expectations for giving and receiving feedback:

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

Day 1 Agenda: 

Additional Notes: