Skip to content

Instantly share code, notes, and snippets.

@Shakikka
Last active December 9, 2020 00:33
Show Gist options
  • Select an option

  • Save Shakikka/dac8bd45a23c1d67bdb893d95e74bab4 to your computer and use it in GitHub Desktop.

Select an option

Save Shakikka/dac8bd45a23c1d67bdb893d95e74bab4 to your computer and use it in GitHub Desktop.
RomCom 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? Learn further with JavaScript, and learn about how it interacts and connects with html and css.
* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? We are going to try pair programming, switching off between navigator and driver with each iteration, while we both go through the project code togther. divide-and-conquer might be good for future projects, however it seems daunting for now.
* How do you communicate best? How do you appreciate receiving communication from others? I communicate best verbally and visually, and appreciate recieving communication in the same manner.
* How would you describe your work style? We're both pretty solo workers, and appreciate silance. We both enjoy flow states and unscheduled breaks.
* What are each of our strengths? How can our strengths complement each other? I enjoy puzzled and am very visual, and Chuck is very contemplative, resulting in well thought out code. These can compliment each other, because deep thinking and puzzle solving will hopefully create excellent code.
* How will we set direction and make decisions as a team? Make a loose outline, and then agree upon each other's changes.
* How will we overcome obstacles? Communication.
* What do you need (resources, environment, communication) to do your best work? Quiet, and a comfortable work spot.
* What scheduling restraints do you have? What are your scheduling preferences? Dinner with family, and other family business.
* What is your style for giving feedback? Does anything ever hold you back from giving feedback? Curt 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? We like that seratonin rush of passing a test, and we're pretty good at buckling down and staying focused. We could use improvement in fully reading test code, and I could use improvement in spelling.
* What tools do you want to use to manage the project? Google, atom, wipe board, toby extension, tuple, slack.
* How do you want the group to solve problems when members run into issues with features of the project? Together.
* How do you know if a project is successful? How can we achieve that as a group? If our code works and we learned something. Testing, communication, and refactoring together.
* How will we recognize each other's successes and celebrate them? Virtual high-fives. Verbally acknowleding when the other person does a good job or has a good idea.
### Remote Work Considerations During the COVID-19 Quarantine
* 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? Roommates, family, pets. Scheduling, noise canceling headphones, communication with others.
* 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. Library/schedule Turing time.
* 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? We don't like Pomodoro technique, but we will take a break when we feel like it.
* 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? Communication and private messages in slack updating each other about our situations.
### Template for DTR Memo
Project: Romcom
Group Member Names:Joel Thomas, Chuck Morris.
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?): Learn more about JavaScript and how it interacts with css and html.
Team strengths & collaboration styles (consider discussing your Pairin qualities here): Paired collab, hunkering down and deep thinking.
How we can use our strengths to overcome obstacles: see above
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): see above
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?): see above
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): see above
Workload Expectations (What features do we each want to work on?): see above
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): see above
Expectations for giving and receiving feedback: see above
Additional Remote Considerations: see above. Chuck's internet goes out occasionally
Project management tools we will use (GitHub projects or Trello are popular tools): see above
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment