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:
ANDREW BEN AND SCOTT
What are each of our learning goals for this project? What drives us in this project? Andrew: Writing JS intentionally. Ben: Implementing more parameters and arg's in JS. Guessing with CSS. Scott: Writing JS more fluidly, with intention.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? Andrew: Enjoys collaborating, but also solo problem solving. pair vs divide and conq = both have value. Ben: would like more time with pair programming for the xp. While in the building, paired has a lot of value. Scott: love collab - but would love more xp with divide and conq. Would like to focus on building solo fluidity.
How do you communicate best? How do you appreciate receiving communication from others? Andrew: open, direct communication. Ben: type doesnt matter too much, text catches attention quickly, slack closely behind. Appreciated specific feedback, actionable. Stand-up check-ins to make sure we aren't stepping on each other. Scott: Text is a good way to get a hold of me quickly, slack next. Same as ben: specific actionable feeback appreciated.
How would you describe your work style? Andrew: Thinking, processing before taking action. Ben: sometimes fast and loose, but appreciates taking time to make a plan to avoid refactoring. Scott: similar to andrew. blocks of flex time after lessons to digest, review or ramp up to proj. work.
What are each of our strengths? How can our strengths complement each other? Andrew: eager, motivated to get into the proj. Ben: Similar to the other two. Scott: Looking at my current gaps in understanding as opportunities for learning. focused on relationships, builiding and maintaining.
What’s gone well or poorly in your previous projects? Andrew: teamwork was lacking, so looking forward to building each other up. Ben: similar to Andrew - would like to make sure that we know where we are at. Scott: teamwork was a strength, but looking forward to testing individual problem solving.
How will we set direction and make decisions as a team? Team Answer: The comp is the direction - MVP. Talking through the options for the decision at hand. Iteration by iteration.
How will we overcome obstacles? Being direct - talk to the person first. Address issues quickly. Stand-ups or quick slack messages when issues arrive.
What do you need (resources, environment, communication) to do your best work? Switch locations to switch mindsets. quiet space. space to learn with each other. no assumptions about where we should be with our learning.
What scheduling restraints do you have? What are your scheduling preferences? Andrew: none. arrive at 9 Ben: none. arrive at 8 am Scott: none. arrive at 7. Hard cut-off times are helpful. if staying late - gotta have a dinner break.
What is your style for giving feedback? Does anything ever hold you back from giving feedback? Andrew: Stay positive. Be Honest Ben: Ditto Scott: ditto - maybe frequent feedback as a focus.
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? Andrew: Strengths: CSS room for improvement: JS. Ben: Strengths: JS room for improvement: Flex Scott: Strengths: CSS room for improvement: JS, general Arguments and params.
What tools do you want to use to manage the project? Github Projects
How do you want the group to solve problems when members run into issues with features of the project? Andrew: Ask for help, start with partners. Ben: ditto the others. Scott: 45min struggle timer THEN ASK FOR HELP.
How do you know if a project is successful? How can we achieve that as a group? did we grow? are we > we were? How will we recognize each other's successes and celebrate them? High fives - Vocalizing specific successes. Keeping it positive.
Any additional questions that you would like to add:
Template for DTR Memo 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?):
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
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):
Expectations for giving and receiving feedback:
Project management tools we will use (GitHub projects or Trello are popular tools):
Day 1 Agenda:
Additional Notes: