Skip to content

Instantly share code, notes, and snippets.

@Jessiewithani
Created May 6, 2019 22:46
Show Gist options
  • Save Jessiewithani/d1b76d5e334ff6ead3901889da19b515 to your computer and use it in GitHub Desktop.
Save Jessiewithani/d1b76d5e334ff6ead3901889da19b515 to your computer and use it in GitHub Desktop.

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 each of our learning goals for this project? What drives us in this project? What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? How do you communicate best? How do you appreciate receiving communication from others? How would you describe your work style? What are each of our strengths? How can our strengths complement each other? What’s gone well or poorly in your previous projects? How will we set direction and make decisions as a team? How will we overcome obstacles? What do you need (resources, environment, communication) to do your best work? What scheduling restraints do you have? What are your scheduling preferences? What is your style for giving feedback? Does anything ever hold you back from giving feedback? 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? What tools do you want to use to manage the project? How do you want the group to solve problems when members run into issues with features of the project? How do you know if a project is successful? How can we achieve that as a group? How will we recognize each other's successes and celebrate them? Any additional questions that you would like to add:

Template for DTR Memo Project:

Group Member Names: Naomi Campos, Jessie Le-Ho

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

  • Understand JavaScript
  • Better understanding of designing layouts
  • Will feel successful if we have a well designed functional webpage
  • Improving collaboration skills

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

Naomi: really direct, may come off too strong, open to suggestions, takes criticism well, 50/50 collaborative style Jessie: blunt, can take critism, 50/50 "",

How we can use our strengths to overcome obstacles:

  • neither one is going to be afraid to speak up
  • will have good communication

Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Naomi: fine with late hours Jessie: late hours are good

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

  • open and direct
  • no passive agression
  • pros and cons

Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Naomi: good handle on HTML, more improvement on CSS, and comprehend js Jessie: more comfortable with CSS, then HTML, and comprehend js

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

Naomi: section by section, more CSS Jessie: "" more HTML

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

  • JUST DO IT
  • Review notes, practice implementing tools, practice examples, individual research/studying

Expectations for giving and receiving feedback:

  • BE OPEN MINDED

Project management tools we will use:

  • calendar (setting deadlines)
  • timers
  • slack/zoom

Day 1 Agenda: SEMANTIC HTML FORMATTING

Additional Notes: N/A

@allisonreusinger
Copy link

Nice work here!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment