Skip to content

Instantly share code, notes, and snippets.

@lundgrea
Last active May 7, 2019 17:47
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save lundgrea/f0c7819493a1e3a98559c007c1ec8257 to your computer and use it in GitHub Desktop.
Save lundgrea/f0c7819493a1e3a98559c007c1ec8257 to your computer and use it in GitHub Desktop.
Mod1_NumberGuesser_DTR

DTR: Define the Relationship

DTR Memo

Project: Number Guesser

Group Member Names: Noah Gibson, Alyssa Lundgren

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

  • Average of Advanced Beginner and Proficient on the project as a whole
  • Submitted on time
  • Get our hands dirty with JavaScript
  • Great communication between the teammates
  • Mutual understanding of the project and it's steps, equal learning opportunities
  • Meet mid-project deliverable timeline/stay on schedule
  • Try all three pairing styles
  • Work as a team using Git and GitHub

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

  • AJL: Cooperative-Practical, Ace Acehiver, People Developer, Lover of Justice
  • NG: Objective-Analytical, Searcher, I "Get" You, Lover of Wisdom and Knowledge
  • Team: Communication, different individual strengths, open availability, good to work day or night

How we can use our strengths to overcome obstacles:

  • We are going to totally nail communiation.
  • On the same page as far as project kickoff and immediate needs.

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

  • Available to work together: open
  • Individually: open
  • Constraints: bed at ten

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

  • Daily in the morning (8-8:30am)
  • Slack, email, phone/text, zoom
  • Collaboratively

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

  • JavaScript is a stretch for us, but we want to be ballers at the end
  • Feeling pretty good about CSS, HTML

Workload Expectations (What features do we each want to work on?):

  • We are curious about how Git and GitHub will work on this project

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

  • Equal learning opportunities
  • We are curious about how Git and GitHub will work on this project

Expectations for giving and receiving feedback:

  • Kind and honest
  • With the goal in mind

Project management tools we will use:

  • Wireframing our schedule and progress
  • Git and GitHub

Day 1 Agenda:

  • Submit our DTR
  • Setup Git and GitHub on our project and see how merging code looks
  • Wireframe
  • HTML built out

Additional Questions:

What are each of our learning goals for this project? What drives us in this project? What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? How do you communicate best? How do you appreciate receiving communication from others? How would you describe your work style? What are each of our strengths? How can our strengths complement each other? What’s gone well or poorly in your previous projects? How will we set direction and make decisions as a team? How will we overcome obstacles? What do you need (resources, environment, communication) to do your best work? What scheduling restraints do you have? What are your scheduling preferences? What is your style for giving feedback? Does anything ever hold you back from giving feedback? 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? What tools do you want to use to manage the project? How do you want the group to solve problems when members run into issues with features of the project? How do you know if a project is successful? How can we achieve that as a group? How will we recognize each other's successes and celebrate them? Any additional questions that you would like to add:

Additional Notes:

@allisonreusinger
Copy link

I agree that you're definitely nailing communication! Nice work with the level of expectation-setting here!

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