DTR

DTR: Define the Relationship
Use this template 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?

Clearly understand every line of code we make; continue to learn and grow through mod 1.

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

We feel that pair programming and working together will be the best route for our success.

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

Using the slack channel, sharing ideas, alowing space for questions, and checking for understanding (I statements).

How would you describe your work style?

Working hard, efficiently, and with breaks/self care.

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

Cameron - interpersonal; Stacy - problemsolving
These complement eachother by allowing us to look at the task(s) thuroghly.

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

Poorly - Waiting too long to ask for help; trying to force code
Well - comunicating with others for further understanding (on same page)

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

Project plan out and communication!

How will we overcome obstacles?

Communication/reach out for help.

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

To have options.

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

Kids, long classes, family, etc. 

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

Non confrentational, create common ground and check for understanding.

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?

Writing functions, for loops, and if statments without looking up doccumentation. Improvement needed for getting more agile with the code. Ask questions and explain what what is happening/where we are going.

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

Tuple, zoom, google calender, and github projects manager.

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

Ask questions, psudocode/find a direction, and think it out.

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

Running our own tests. Run these tests individually, and/or as a group. Check for understanding.

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

Comunicating success (big/small).

Any additional questions that you would like to add:

Remote Work Considerations During the COVID-19 Quarantine
What does remote focus look like for you? (headphones, distractions minimized (tv, family stuff, etc), video on)

Indivdualistic

When working from the same place where you live, life can get in the way. What are some potential life things that could interfere with your ability to focus, and what plan can we come up with to approach those issues? (Examples: my kids, my dog, my partner, etc.)
If we encounter issues such as power outages, Zoom difficulties, or bad wifi, what backup plans can we have in place? (This could have answers like asking a neighbor to borrow wifi, using cellphone hotspot for internet, switching to slack or skype.
Pomodoro breaks are especially important for remote work and doubly so for quarantine. What should our Pom cadence look like? How will hold ourselves accountable?

Paying attention to cues, and a timer (30 min).

Quarantine is tough, so it’s important to make note of our mental/emotional state when working with others. How can we make space to check in on each other’s well being, in addition to the work that needs to be done?
Template for DTR Memo
Project:

Group Member Names: Stacy and Cameron

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

  Clearly understand every line of code we make; continue to learn and grow through mod 1. By having an understanding, achieving goal of 3s on rubric.

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

  Cameron - interpersonal; Stacy - problemsolving
  These complement eachother by allowing us to look at the task(s) thoroughly.

How we can use our strengths to overcome obstacles:

  Communication/reach out for help.

Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):

  Kids, long classes, family, etc. Useing project time, working lunches, meeting before and after class, and weekends. 

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):

  Daily check-ins via slack and vido. Being personable and checking how things are going. 

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

  Writing functions, for loops, and if statments without looking up doccumentation. Improvement needed for getting more agile with the code. Ask questions and explain what what is happening/where we are going.

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

  Alternating driver/navigator rolls.

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

  Regular commits with appropriate messages. Check and refactor code. 

Pomodoro Break Schedule:

  Every 30 minutes or as needed.

Expectations for giving and receiving feedback:
  
  Kindness, openess, unnecessary pride

Additional Remote Considerations:
  
  Internet connectivity 

Project management tools we will use (GitHub projects or Trello are popular tools):
  
  Tuple, zoom, google calender, and github projects manager.

Day 1 Agenda:

1. Complete Day 1 deliverable
2. Set agenda for Wednesday 


Additional Notes: