DTR

DTR for Quinn and DTR for Averi

DTR with Averi: 
What are your learning goals for this project? 
Averi: Clear understanding of what’s going on...what the code is doing.
Meg:  Understand modules better and how we can use them within classes. Also, to better understand how to use data within a CSV.
 What drives us in this project?
Averi: Moving on to Mod 2 
Meg: Same as Averi… moving on to Mod 2 with a better understanding of ruby necessities 
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
Averi: I prefer pair programming...divide-and-conquer makes me nervous
Meg: I also prefer paired programming
How do you communicate best? How do you appreciate receiving communication from others?
Averi: I prefer in person conversations if its confrontational related. Otherwise, text, slack, call.
Meg: Same as Averi.. If we need to communicate about the project specifically, I prefer to do it in person or via screen share if meeting is not possible.
How would you describe your work style?
Averi: Quiet, place with few distractions. After 90 minutes, I like to take a short break (stretch).
Meg: I find myself getting really caught up in working, and tend power through, but I also need to force myself to take breaks. I also prefer working in a more quiet environment.
What are your strengths? How can our strengths complement each other?
Averi: I’m laid back, I love to learn and solve problems
Meg: I am very logical and analytical with my work. I also want everyone to get along and try to preserve harmony amongst groups.
What’s gone well or poorly in your previous projects?
Averi: When I understand something...I use to shut-down, get quiet, get caught up in my thoughts. But now I’m embracing being uncomfortable.
Meg: When I don’t understand something I get frustrated and just don’t take a break. I also don’t ask people for help as much as I should.  
How will we set direction and make decisions as a team?
 We’ll talk about and work together and an understanding of each of others time.
How will we overcome obstacles?
We’ll ask for help, pair with others and make sure we both understand the process before moving on.
What do you need (resources, environment, communication) to do your best work?
Good communication and quiet environment
What scheduling restraints do you have? What are your scheduling preferences?
Averi: I have child so I can’t work after 6:30 (tue and thur) 5:30 (m,w,f) IN PERSON. Weekends are ok but no late Sundays.
Meg: I am unable to work during lunches, but can stay after school and any time during the weekends. On the weekends, I would prefer to not work too late. 
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
Averi: I prefer in person...constructive
Meg: Same
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?
Averi: Learning to break big, complex problems into small problems
Meg: I feel good about return values, but I struggle with breaking up my methods into smaller ones. I benefit when we talk through the code together. 
What tools do you want to use to manage the project?
Averi: Computer, Github, Slack
Meg: Yes me too … same!
How do you want the group to solve problems when members run into issues with features of the project?
Averi: Ask for help if we don’t know the answer and talk about it in person if it’s an issue between us.
Meg: All conflict should be solved in person, I believe. And any problems with code, I’d like to address by asking others for help, and pairing with higher mods or mentors.
How do you know if a project is successful? How can we achieve that as a group?
Averi: As long as we both have learnt something 
Meg: If Brian smiles… but really, if we pass through iterations and we feel CONFIDENT	 at the end, and excited to show it off!!
How will we recognize each other's successes and celebrate them?
Averi: When she tells me…
Meg: We will give high fives




DTR with Quinn:
Group Member Names: Quinn, Meg

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

Use less instance variables and work on creating more helper methods. Get more familiar with Git and Github workflow.

Goals and expectations:  Use driver navigator. Anytime someone has an idea they become the navigator. Driver doesn't type without being told what to type.

Team strengths: Analytical and Harmony

How to overcome obstacles: Work in person to avoid vocabulary problems. When questions come up over code use our resources first but also reach out to upper mods or mentors.

Schedule Expectations (When are we available to work together and individually?):
Over weekend both study the project individually and create code. Early Monday collaborate our work. Also work after school if possible

Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): Slack over texting. Text to initiate slack conversation.

Abilities Expectations (Technical strengths and areas for desired improvement):
Improve vocab, workflow, and heper methods

Workload Expectations (What features do we each want to work on?):
Over the weekend we will both work on code/ideas. On monday decide if we need to pass code back and forth.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):

Meg will be in charge of merging and reviewing code.

Expectations for giving and receiving feedback:

Be honest and compassionate.