Kyle & Karl DTR.md

DTR: Define the Relationship

One teammate should copy and paste the raw markdown into a gist of your own.

Guiding Questions to Define The Relationship:

Schedule: communicate at noon what our after school workflow will be. No Friday after 4pm for Kyle Tuesday & Thursday & Saturday is Honey Openings for Karl - will prioritize getting work done before checking out. Stay in communication about schedule/progress.

• What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? Part divide & conquer, part collaboration depending on outside life commitments. Define targets to have completed by end of day(s).

• How do you communicate best? How do you appreciate receiving communication from others? Kyle - Blunt & clear communication - shares openly and can parkinglot something if it needs to be revisited. Karl - Allowing space to think and then come to the table with both ideas. Poke holes in Kyle's reasoning if there is disparity in the way to move forward.

• How would you describe your work style? Kyle - When at Turing it's work time. Home life is not. Work for longer stints then break for longer than 5 mins. Karl - Staying focused on coding when it's work time.

• What are each of our strengths? How can our strengths complement each other? Kyle - JS functionality. Helping/nurturing towards understanding. Picking apart code from internet to impliment into projects in applicable capacity.
  Karl - HTML & CSS, Self-Care, Both - Asking for help when needed.

• What’s gone well or poorly in your previous projects? Didn't look at the style guides. Clearly naming id's & classes to clearly communicate what's happening for each other's understanding.

• How will we set direction and make decisions as a team? Break down tasks and assign work load. Divide up work based on what we aren't so comfortable with so we can learn and grow in our weak points.

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

• What scheduling restraints do you have? What are your scheduling preferences? Previously discussed above.

• What is your style for giving feedback? Does anything ever hold you back from giving feedback? Kyle - avoid conflict especially in child ego. Karl - NVC focused.
  Both - Committed to Adult - Adult communication.

• What do you identify as being your biggest strength(s) technically? Where do you feel you could use improvement in your technical skills? How can our team help support you in improving these skills? Previously Discussed

• How do you want the group to solve problems when members run into issues with features of the project? Driver-navigator system so there's a teaching to fish dynamic occurring. Ping pong or ask for outside help if neither know.

• How do you know if a project is successful? How can we achieve that as a group? When the intended lessons are learned, when the project is done well, when the ruberic is achieved!

• How will we recognize each other's successes and celebrate them? High Fives, slack props in the form of gifs and puns.

Any additional questions that you would like to add:

Template for DTR Memo

Project: 1911 Mod 1 Pair Project

Group Member Names: Karl & Kyle

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? YES, you can still fully answer this question without knowing exactly what you're going to build.): Impliment appropriately styled css & html based on style guide expectations. Expand understanding with JS and functionality of building an app. Success will look like a working app that hits a 3 in all categories and kyle wants a 4 in JS.

Team strengths & collaboration styles (consider discussing your Pairin qualities here): Mutually desiring to nurture the other one in a capacity that will support the learning process without showing or giving help that takes away from the intended learning.

How we can use our strengths to overcome obstacles: Check in daily to see how the code is standing up against the ruberic and make sure all expectations are being met. Communicating challenges as they are happening to stay connected on progress and challenges as well as wins and progress.

What do you need to look out for, in terms of strengths/working styles coming into conflict? Show other ways of reasoning/thinking that are equally valid or true.

Schedule Expectations (When are we available to work together and individually? What constraints do we have?): 7:30-9am morning work time. 4-7:30 work time at Turing, discuss later working hours if necessary or fewer if saturdated. Friday nights are out.

What is the one hour/day that each teammate has on their calendar for personal study/practice time? Kyle can utilize morning time. Karl can utilize friday after school.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): Communicate which tiles feel comfortable/challenging to distribute work load that balances strengths/weaknesses to get a well rounded experience.

Communicate when we finish a tile.

Communicate when we need help or if having difficulty working on the current tile.

Utilize partner for help first, then rocks or mentors if we are both stuck.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Karl wants to get fresh with JS, Kyle wants to level up CSS. Activate learning: GO!

Expectations for giving and receiving feedback: Clear honest communication using non-violence and fact based observations.

Additional Notes: We are done DTRing.