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?

  Learn new material outlined in project learning goals.

• What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?

  Work together on inital user stories, and then divide later ones per partner.

• How do you communicate best? How do you appreciate receiving communication from others?

  Communicate and work in person as much as possible, and communicate by Slack after school.

• How would you describe your work style?

  Do prework by ourselves and come prepared.

• What are each of our strengths? How can our strengths complement each other?

  Getting goals accomplished on time.

• What’s gone well or poorly in your previous projects?

  Reach out to each other first if there is a problem we are stuck on. Then, we can reach out to other people. Asking questions proactively.

• How will we set direction and make decisions as a team?

  Aim to complete 2-3 user stories every day. Communicate as much as possible.

• How will we overcome obstacles?

  We anticipate learning obstacles, but we should prioritize our time to move on when we encounter something we are stuck on.

• What do you need (resources, environment, communication) to do your best work?

  Project worktime and planning which user stories to complete each day.

• What scheduling restraints do you have? What are your scheduling preferences?

  Execept for Tuesdays, and weekends, we can work during project worktime and possibly later until 6pm, if need be.

• What is your style for giving feedback? Does anything ever hold you back from giving feedback?

  Communicate as much as possible

• 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?

  We need to work on time management, but we are good at searching/googling for answers to problems.

• What tools do you want to use to manage the project?

  Projectboard.

• How do you want the group to solve problems when members run into issues with features of the project?

  Reach out to each other and then other people to solve problems that we can't solve on our own.

• How do you know if a project is successful? How can we achieve that as a group?

  That we have passed the project.

• How will we recognize each other's successes and celebrate them?

  Document log of errors and how we overcame those errors.

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: