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:
What are your learning goals for this project? What drives us in this project?
- Obtaining DOM manipultion.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- Both have value, and some work better than others depending on the groups interaction with each other.
How do you communicate best? How do you appreciate receiving communication from others?
- Through text or in person. Up to date and on the spot.
How would you describe your work style?
- I like to tackle multiple problems and digest them as we go so learning can be efficient.
What are your strengths? How can our strengths complement each other?
- I am a hard worker. Very organized. Available when you need me.
What’s gone well or poorly in your previous projects?
- Commuication was awesome, pairing should have increased.
How will we set direction and make decisions as a team?
- Using Waffle
How will we overcome obstacles?
- Together if that is needed.
What do you need (resources, environment, communication) to do your best work?
- Peace and quiet!
What scheduling restraints do you have? What are your scheduling preferences?
- I have none. Walk my dog.
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
- Direct and to the point but tactful. Usually never unless it's a superior.
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?
- My biggest strength is organization and cleanliness of writing code.
What tools do you want to use to manage the project?
- Waffle
How do you want the group to solve problems when members run into issues with features of the project?
- Together and or with a pairing.
How do you know if a project is successful? How can we achieve that as a group?
- We feel that we learned along the way.
How will we recognize each other's successes and celebrate them?
- By creating task and mini-achievements with goals along the way that are obtainable.
Any additional questions that you would like to add:
Template for DTR Memo
Project: Linked-List
Group Member Names: Ben & Sam
Project Expectations: A better understanding of DOM and Javascript
Goals and expectations: Learning improvement
Team strengths: Collaboration!
How to overcome obstacles: Together and with outside help.
Schedule Expectations (When are we available to work together and individually?): Openly available most the time
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): Text!
Abilities Expectations (Technical strengths and areas for desired improvement): Coding in general
Workload Expectations (What features do we each want to work on?): Divide and conquer
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): This will be a learning opportunity as well
Expectations for giving and receiving feedback: Direct and to the point.
Agenda to discuss project launch: Day of meeting and regular meetings throughout.
Ideas: Tackle the HTML/CSS continue to functionality
Tools: Whatever will best suit us in the moment.
Additional Notes: Let's tackle this together!