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.
-
What are each of our learning goals for this project? What drives us in this project? Work with someone else's code that I'm unfamiliar with, and further my understanding of rails
-
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? If possible, I prefer divide-and-conquer approaches with emphasis on communication
-
How do you communicate best? How do you appreciate receiving communication from others? Slack
-
How would you describe your work style? poms,
-
What are each of our strengths? How can our strengths complement each other? Strong understanding of coding theory
-
What's gone well or poorly in your previous projects? Structure and planning
-
How will we set direction and make decisions as a team? Stand ups before worktime
-
How will we overcome obstacles? Try, Pry, Cry, ask for Help
-
What do you need (resources, environment, communication) to do your best work? Regular and every day, just before worktime
-
What scheduling restraints do you have? What are your scheduling preferences? 9am - 10pm
-
What is your style for giving feedback? Does anything ever hold you back from giving feedback? As it comes up, but I have a hard time confronting personality issues
-
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? Understanding the flow of the code
weakness (both) css
-
What tools do you want to use to manage the project? Github Project boards
-
How do you want the group to solve problems when members run into issues with features of the project? 20 min slack call
-
How do you know if a project is successful? How can we achieve that as a group? Get 3s
-
How will we recognize each other's successes and celebrate them?
Any additional questions that you would like to add:
-
What does remote focus look like for you? (headphones, distractions minimized (tv, family stuff, etc), video on) Music, headphones, distractions minimized, no face cam
-
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.) Train sounds
-
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? I prefer 25 min on 5 min off
-
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? I like to keep my personal feelings
Project: Group Member Names: 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?): Team strengths & collaboration styles (consider discussing your Pairin qualities here): How we can use our strengths to overcome obstacles: 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): 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?): Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Workload Expectations (What features do we each want to work on?): Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Pomodoro Break Schedule: Expectations for giving and receiving feedback: Additional Remote Considerations: Project management tools we will use (GitHub projects or Trello are popular tools): Day 1 Agenda: Additional Notes: