Skip to content

Instantly share code, notes, and snippets.

@aemiers

aemiers/DTR.md

Last active October 14, 2020 14:07
Show Gist options
  • Save aemiers/09d85c9ba7cb38f8e908509740f5b8ce to your computer and use it in GitHub Desktop.
Save aemiers/09d85c9ba7cb38f8e908509740f5b8ce to your computer and use it in GitHub Desktop.
Download ZIP
Raw
DTR.md

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?

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

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)

  • When working from the same place where you live, life can get in the way. What are some potential life things that could affect your ability to focus, and what plan can we come up with to approach those moments?

  • 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? 25 minutes before POM, 5 minute break or whatever is needed.

  • 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: Hang In There Paired Project

Group Member Names: Cameron Aragon, Anneke Miers

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

  • Cameron's Learning Goals - I want to understand how HTML, CSS, and JS all interact with one another. I also want to understand the development process of a website. I would also like to build upon my current JS knowledge and strengthen those skills.

  • Annie's Learning Goals - I would love to improve on my collaboration skills with another developer. In strengthening this relationship, I hope to also improve my JS skills, learn the basics of HTML and CSS, and understand how these three languages talk to one another.

  • Combined Goal - Becoming comfortable reaching out to mentors, upper mods, and/or the Turing community to ask for help or guidance (as a last resort after all the research and problem solving on our end).

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

  • Cameron's preferred work environment is quiet. Annie's is a combination of quiet personal work time combined with group collaboration for when she gets stuck.

  • Cameron's - cooperative-practical, friend, i get you, and lover of humanity Annie's - cooperative-practical, standout, at your service, and lover of justice

How we can use our strengths to overcome obstacles:

  • We both have cooperative-practical in common. Annie could use her standout for when the group needs something. Cameron can use his "I get you" when Annie is struggling. It looks like both of our strengths are very kind-human-oriented.

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

  • Mornings are off limits to both of us, but we are available from 5-10pm every week day, and all day, every day on the weekends. If one of our internets goes out, the other person is welcome to join the other at their place or at a coffee house.

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

  • Slack, GitHub, Zoom, CodePen, Repl.it, pull request templates, Google Calendar

  • We both have open and honest collaboration/communication styles. We believe that a balance of paired programming and divide-and-conquer methods should be utilized to help both of us grow the the fullest of our project potential.

  • Zoom or in-person communication are the best for us. Slack is not so good for Cameron in terms of collaboration, but in terms of scheduling, Slack works perfectly fine.

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

  • Annie has had a little background experience with HTML and CSS, so she views that as a strength early on. Cameron's technical strength is his ability to conceptualize code and how problem solving.

  • Annie feels that she could use improvement in coding JS and problem solving, which working with Cameron as he's vocalizing his process will help. Cameron's weakness would be vocalizing his process, so commenting the process to Annie will help him in this.

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

  • Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques

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

  • Over communicate at first, neither of us have done this sort of project before, so we will touch base after we have examined the work load

Pomodoro Break Schedule:

  • 25 minutes of work, 5 minutes of break

Expectations for giving and receiving feedback:

  • Open and honest communication, constructive feedback is always welcome in both of our eyes.

Additional Remote Considerations:

  • Both of us have quiet environments and feel comfortable meeting in person and/or over Zoom if need be.

Project management tools we will use (GitHub projects or Trello are popular tools):

  • GitHub projects

Day 1 Agenda:

  • Complete DTR together
  • Fork and clone the repo
  • Read all of the instructions and the rubric again
  • Add all teammates and instructor (Hannah) to forked repo as collaborators
  • Share link with our project manager

Additional Notes:

We are shooting for 4's, but realistically, if we get 3's, we will be acceptable. We also believe that if we learn something, this project is a success. Growth is the main goal. As long as we continue forward and try on the project, we will learn something!

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