DTR - Linked List - Rob Morgan and Matt Renn

gistfile1.txt

# 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?

Learning to pair effectively.  Improve JS skills.  Get better at writing functions.  Writing code understandable to any programmer.

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

We'll start with driver/navigator.  We don't think we need divide-and-conquer for this project.  But we'll change that if necessary.

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

Consistency and honesty.  Slack is good.

* How would you describe your work style?

Pragmatic and methodical.  Want to know exactly what is happening.

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

Technical: Matt - semantic HTML, navigating computer, github workflow, improving in JS;  Rob - HTML and CSS, design, working on JS
Personal: Matt - observant, open, honest in communication, schedule is open;  Rob - analytical, determined, schedule is easy

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

Following directions carefully, didn't get stuck for too long, patience.  Got help from mod2 people.

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

Communicate.

* How will we overcome obstacles?

Technical problems - go find help.  Personal - refer to DTR.  Communicate.

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

Sleep, start early, don't fall behind, communicate consistently about problems and/or solutions.

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

Saturday/Sunday mornings may be tricky.
Matt: no Tuesday morning, 29th
      no Wednesday afternoon at 2:30

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

Verbal.  Terse.  To the point.

* 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?

See above for strengths.
Weaknesses: Matt - writing functions, CSS
            Rob - general JS

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

Slack, github, school, teamwork

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

If it's technical, we'll get help.  We'll pair up with mod2 people.

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

Firstly, if we get through the spec.  Second, if we're satisfied with the functionality and clarity, the ends and the means.

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

Fist bumps.

Any additional questions that you would like to add:






### Template for DTR Memo

Project: 

Group Member Names:

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

Goals and expectations:
	
Team strengths:

How to overcome obstacles:

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

Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):

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

Expectations for giving and receiving feedback:

Agenda to discuss project launch:

Ideas:
 
Tools: 

Additional Notes: