DTR Number Guesser

# DTR: Define the Relationship

### Guiding Questions to Define The Relationship:

* What are each of our learning goals for this project? What drives us in this project?
Roger: want to get more fluent with HTML structure, look at a page and be confident in writin gthe HTML & CSS to produce. Also learn Javascript. Drive: to be a more well rounded developer.
Matt:I want to work on my Javascript logic as well as CSS flexbox layout for mobile and desktop.
* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
Roger: New to pair programming. In the past had exclusively worked using divide-and-conquer, sees pair programming as a valauble approach workig with new material.
Matt: Is a fan of paired programming because of how you can bounce ideas off eachother in the moment.
* How do you communicate best? How do you appreciate receiving communication from others?
Roger: Communicate best: full open, honest communication. Receives: Wants direct communication.
Matt: Likes the why's behind things so when explaing to Matt, having the why is very important.
* How would you describe your work style?
Roger: have a structured work ethic, have alloted work time and likes to complete HTML then CSS then Javascript. Prefers longer blocks to get work done with nice breaks inbetween.
Matt: I like to draw out the webstie then move onto HTML then CSS and Javascript combined as the site is built.
* What are each of our strengths? How can our strengths complement each other?
Roger: Very adaptable, and adapt his work ethic to make things work with a partner.
Matt: Logical with lots of leadership and project planning experience. 
* What’s gone well or poorly in your previous projects?
Roger: previous expereince is heavy on taking orders and following them out.
Matt: setting daily goals to achive that build out the project. 
* How will we set direction and make decisions as a team?
Roger: Open, honest communication. Set daily goals yet stay adaptable. Reach out to mentors as well as upper mod students.
* How will we overcome obstacles?
Roger: as a team. Talk through things and reach out to our support system.
Matt: talking about all the shit, good and bad. 
* What do you need (resources, environment, communication) to do your best work?
Roger: Ideal work is at 2am, but is very flexiable on when and where to work.
Matt: Definitely not at home. Listen to music as I work. 
* What scheduling restraints do you have? What are your scheduling preferences?
Roger: Has a pregnant wife and a child and working around them. Has to be home by 8pm but can work outside the house either at Turing or at a coffee shop.
Matt: None really, just need to get a workout in and I need to eat all the time.
* What is your style for giving feedback? Does anything ever hold you back from giving feedback?
Roger: very open and honest, not sugar coated.
Matt: Please provide the why of what you are giving feedback on.
* 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?
Roger: Javascript is an oppertunity to improve in, much stronger in HTML and CSS. Making things Desktop to mobile is something Roger is looking to learn more.
Matt: Has previous experience with Javascript, making mobile versions of websites.
* What tools do you want to use to manage the project?
Floobits, use BEM layout, daily to do lists, sublime, chating both audio and video.
* How do you want the group to solve problems when members run into issues with features of the project?
Look at what we have done using logic to see what we know and can apply, research on the line, use mentors and upper mod students.
* How do you know if a project is successful? How can we achieve that as a group?
We hit the desired rubric points as well as growing stronger in the material and knowhow. 
* How will we recognize each other's successes and celebrate them?
celebreate when we hit MVP (minimum viable product). Celebrate at brothers all the success we've had!

Any additional questions that you would like to add:

### Template for DTR Memo

Project: Number Guesser

Group Member Names: Roger Hugehs & Matthew Malone

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?):
Want to become more successful developers and produce a shipable MVP.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
Roger is adaptable and Matt has leadership and project planning experience.
How we can use our strengths to overcome obstacles:
Roger can adapt time and styles to accomadate the other people in the group while Matthew can help plan out the project to accomplish the shipable MVP.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
Roger: Has a pregnant wife and a child and working around them. Has to be home by 8pm but can work outside the house either at Turing or at a coffee shop.
Matt: None really, just need to get a workout in and I need to eat all the 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?):
AM Daily checkins and goal settings for the day. Communicating via slack. Talk through things out and decide what we want to do.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
Roger: want to get more fluent with HTML structure, look at a page and be confident in writin gthe HTML & CSS to produce. Also learn Javascript. Drive: to be a more well rounded developer.
Matt:I want to work on my Javascript logic as well as CSS flexbox layout for mobile and desktop.
Workload Expectations (What features do we each want to work on?):
Wants to point to any part of the website and be able to describe what it is, what its doing and why.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): 
Don't know yet.
Expectations for giving and receiving feedback:
Roger: Open, honest communication. Set daily goals yet stay adaptable. Reach out to mentors as well as upper mod students.
Project management tools we will use:
Floobits, use BEM layout, daily to do lists, sublime, chating both audio and video.
Day 1 Agenda: 
sketch out the website, divide it into containers and name them and website orginization.
Additional Notes:

Looks good -- appreciate the level of detail here!