DTR_jimmy_tom_michael_nikki

# 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?
Be Jimmy's Friend
Michael: Learning Auth, Nested Resources, Namespacing, Rails Helpers.
Tom: Better understanding of the layout an relationships. Contribute even amount to project.
Jimmy: Similar to Michael. Nested Resources. Reps on everything.
Nikki: Project management. Reps in. 

* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
Michael: Pretty good pairing. Amazing alone.
Tom: With this many user stories, divide and conquer will be needed. Paired programming to build skills. 
Jimmy: Nuetral.
Nikki: Same as Michael

* How do you communicate best? How do you appreciate receiving communication from others?
Michael: Direct communicator. Prefers the same. Let me know if I need to bring it down.
Tom: Tell me what I need to know.
Jimmy: Be brutally honest with me. Let me know. Won't take it personal. Be open to what I have to say/constructive critism.
Nikki: A little sensitive in the feedback I give. Give prompt if need quick honest feedback.

* How would you describe your work style?
Michael: Like to just do. Frustrated with too much planning.
Tom:
Jimmy: Get it done approach.
Nikki: I plan and prep. But get into it. Like lists and checkmarks.

* What are your strengths? How can our strengths complement each other?
Michael: Executing. Strategic Thinking.
Tom:
Jimmy: Influecing. Executing.
Nikki: Relationship Building. Strategic Thinking.

* What’s gone well or poorly in your previous projects?
Michael: Poorly: When noticing things aren't getting done, worked overtime to complete on own. Well: Pretty flexible partners.
Tom:
Jimmy: Poorly: Tests-left to the last minute. Well: Everything else.
Nikki: Poorly: Did not speak up, spent too much time planning/researching. Well: Updating Workplans. 

* How will we set direction and make decisions as a team?
Agile workflow. Choose a direction and adjust as we go along. Constant checkins

* How will we overcome obstacles?
See above. Be flexible.


* What do you need (resources, environment, communication) to do your best work?
Flexible. Queit place. Book study rooms when pairing. Work from home/communicate. Keep attention on OUR project.

* What scheduling restraints do you have? What are your scheduling preferences?
Michael: Wednesday 10/24 afternoon/evening, Friday nights (flexible).
Tom:
Jimmy: Tuesday 10/23 afternoon/evening.
Nikki: Saturday night. 

Pairing afternoons. Pairing/remote pairing weekends. AS NEEDED.

* What is your style for giving feedback? Does anything ever hold you back from giving feedback?
Michael: Direct. 
Tom:
Jimmy: Direct.
Nikki: Ask me for direct.

* 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?
Michael: Strength: Styling Growth:
Tom:
Jimmy: Strength: Growth:
Nikki: Strength: Git/Github, organizational skill. Growth:

* What tools do you want to use to manage the project?
Waffle, github issues, slack, schema visualization.

* How do you want the group to solve problems when members run into issues with features of the project?
Pairing. Ask for help, slack. Pair with Zach.

* How do you know if a project is successful? How can we achieve that as a group?
Completes to instructors expectations. Are able to pair successfully and work remotely as a team. Adjust workplans in an agile workflow.

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

Any additional questions that you would like to add:


### Template for DTR Memo

Project: Book Club

Group Member Names: Michael Gatewood, Tom Nunez, Nikki Holland-Plum, Jimmy Smith

Project Expectations: What does each group member hope to get out of this project? 

Goals and expectations: To complete the project to instructor expectations. Become very strong in our current areas of growth.
	
Team strengths: Styling, git/github, pairing, organization.

How to overcome obstacles: Be direct. Pair. Request help.

Schedule Expectations (When are we available to work together and individually?): Mostly remote work. Pairing as needed to work on needed skills (after school).

Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): Slack, direct communication. Communicate when working on feature, when stuck and when completed.

Abilities Expectations (Technical strengths and areas for desired improvement): Auth, overall repitition.

Workload Expectations (What features do we each want to work on?): Agile workflow, will adjust.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): Code reviews. Use Waffleboard.

Expectations for giving and receiving feedback: Direct. 

Agenda to discuss project launch:
Ideas: Review user stories tonight, decide on stories we want to work on, where we want to start and meet back on it tomorrow. 
Nikki will complete Github repo, empty rails app, waffleboard and this before tomorrow.
  
Tools: Zach, Waffleboard.

Additional Notes: