IdeaBox DTR #1

gistfile1.txt

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 each of our learning goals for this project? What drives us in this project?
  -Learning Goals: Get a firm grasp on all the projects to prepare for check yourself. Try and make our functions as dynamic as possible. Establish a good naming convention for semantic HTML.
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
  -We all seem to do well with divide and conquer, and Pol is comfortable with either. Chris and Brady want some more experience with pair programming.
How do you communicate best? How do you appreciate receiving communication from others?
  -Concise and honest communication is what works best for all team members.
How would you describe your work style?
  -We are all grinders.
What are each of our strengths? How can our strengths complement each other?
  -Pol is calm and collected, Chris is a self-starter, and Brady is a Team-Player. Are strengths all compliment eachother nicely, and we have representation from all three EQ tiers.
What’s gone well or poorly in your previous projects?
  -We need clearly defined and clearly assigned tasks for this project.
How will we set direction and make decisions as a team?
  -We are going to spend a little more time planning, and breaking the tasks on the front end to provide a clearer path forward.
How will we overcome obstacles?
  -Google, classmates, upperclassman, instructors.
What do you need (resources, environment, communication) to do your best work?
  -We work well in quiet environments where we can focus without distractions.
What scheduling restraints do you have? What are your scheduling preferences?
  -Chris is restricted by location/commute, so remote work is going to be his primary. Pol has a longer commute also, so remote is preferred for him. Brady is super flexible, so he will accomodate any schedule.
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
  -Concise, specific, objective, and honest feedback is preferred for all. 
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?
  -Filtering through object properties, and event bubbling are the technical skills we are hoping to develop.
What tools do you want to use to manage the project?
  -Trello, zoom, slack.
How do you want the group to solve problems when members run into issues with features of the project?
  -Utilize your resources to try and problem solve, then reach out to group members.
How do you know if a project is successful? How can we achieve that as a group?
  -Grading Rubric, and how comfortable you are with the concepts.
How will we recognize each other's successes and celebrate them?
  -Through feedback.
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:

Day 1 Agenda:

Additional Notes: