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?
Working on implementing JS with CSS & HTML.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
Start pair programming, go from there to divide up responsibilities. Pair program, continue to check throughout.
How do you communicate best? How do you appreciate receiving communication from others?
Tell it like it is. Objective. Clearly & often communication.
How would you describe your work style?
Kyle: "Ride it to the wheels fall off."
Becca: "3-4 hours working, break 1-2 hours."
What are each of our strengths? How can our strengths complement each other?
Becca: Detail oriented.
Kyle: Attention to detail, typos, etc.
Both pay attention & can sharpen each other.
What’s gone well or poorly in your previous projects?
Struggling too long before reaching out for help.
Figuring out who is in the network for support to "phone help" to.
How will we set direction and make decisions as a team?
Prioritize, break down the problem one step at a time.
How will we overcome obstacles?
Ask each other. Resource outside help.
Research new functionalities, divy that up or combine forces.
What do you need (resources, environment, communication) to do your best work?
Nutrition, rest, outside walk breaks (fresh air).
What scheduling restraints do you have? What are your scheduling preferences?
Mostly free. Try to cut off work time by 9pm. Take it as it goes.
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
K: Doesn't beat around the bush.
B: Pretty vocal about problems.
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?
Need to work on connecting JS with CSS & HTML.
What tools do you want to use to manage the project?
Take POMS frequently
How do you want the group to solve problems when members run into issues with features of the project?
Both look at the problem.
// Make a note on the code editor about the problem to help jog our memory while trying to fix it together.
How do you know if a project is successful? How can we achieve that as a group?
Learning the material (*fluency*)
Check iterations for the code goals
How will we recognize each other's successes and celebrate them?
Virtual pat on the back. Say good job. Good syntax, spacing, method, etc...
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) 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.)
Taking care of our dogs.
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.
Break and come check in later.
Pomodoro breaks are especially important for remote work and doubly so for quarantine. What should our Pom cadence look like? How will we hold ourselves accountable?
At least every 30 min take a POM, 5-10 min break depending.
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?
Use Turing's counseling services.
Take note if the other person is stressed. If we're bogged down, take a break & come back to it later.
Project: Hang In There
Group Member Names: Kyle & Becca
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: