Skip to content

Instantly share code, notes, and snippets.

@ttarlov
Last active February 4, 2020 00:17
Show Gist options
  • Save ttarlov/45c313a0e9fc2cf26a6c5901ebcdbfb7 to your computer and use it in GitHub Desktop.
Save ttarlov/45c313a0e9fc2cf26a6c5901ebcdbfb7 to your computer and use it in GitHub Desktop.
FitLit DTR Memo

DTR: Define the Relationship

Template for DTR Memo

Project: FitLit - 1911 Mod 2 Pair Project

Group Member Names: Taras Tarlov / Karl Nielsen

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?

 - Make sure we have a MVP working. Continue to expand understanding of array prototypes and objects. Practice OOP and TDD. Be professional with our github commits. Comment on all PRs to document evolution of the project. 

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.):

- Both have understanding of the codebase. Expand on our knowledge of main concepts. 

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

- Ability to work well together as we have gotten to know eachother well through our time at Turing so far. 

How we can use our strengths to overcome obstacles:

- Karl is much more optimistic in the face of struggle. We are both not afraid to ask for help. 
 - Take consistent POMS/breaks. 
- Front load the workload. 

What do you need to look out for, in terms of strengths/working styles coming into conflict?

- Communication is the priority. 

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

- Working together until about 7pm at the latest. 
- Weekends are open after noon till 5pmish. 

What is the one hour/day that each teammate has on their calendar for personal study/practice time?

- Evenings after 7pm is personal time. 

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

- Open line of communication over Slack and SMS. 

Abilities & Growth Expectations (Technical strengths and areas for desired improvement):

- Both have a reasonable grasp on the content. Looking to expand understanding of OOP, TDD and git workflow. 

Expectations for giving and receiving feedback:

- Open communication. Not letting things build up. 

Additional Notes:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment