garcia50 · August 25, 2017 22:53
diff --git a/DTR b/DTR
 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 your 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 your 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:
 Template for DTR Memo
 Project: Night Writer
 Group Member Names: Young Jung & Luis Garcia
 Project Expectations: What does each group member hope to get out of this project?  
  We expect to complete the project while obtaining new knowledge. Learn to pair effectively and to learn from each other.  Overall generating real-world practice working with pairs.
 Goals and expectations: Finish the project and do an extension if possible.
 Team strengths: Two heads are better than one.  Both have basic understanding of Ruby, time management skills, flexibility, good at asking questions.  We are expert Google users.
 
 How to overcome obstacles: Working together, communicating openly and directly.
 Schedule Expectations (When are we available to work together and individually?): Young : Not available Saturday 8/26 but otherwise available. Luis : Open schedule, not Saturday.
 Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):  At least once a day, during available project work hours and after/before class.  Use resources like Slack to keep in communication at other times.
 Abilities Expectations (Technical strengths and areas for desired improvement): Young : I want to improve my ability to write code without a specific interaction pattern given and how to break down logic into smaller pieces.  Luis : Want to improve ability to write basic, elementary code without referring to notes, improve memorizing basic coding practices.
 Workload Expectations (What features do we each want to work on?): Luis : Learn File I/O Young : same
 Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): Use branching in Github.
 Expectations for giving and receiving feedback: Be polite but honest.
 Agenda to discuss project launch: Whiteboard project
                                  Split project up
 Ideas:
 Tools:
 Additional Notes:
	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 your 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 your 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:
	Template for DTR Memo
	Project: Night Writer
	Group Member Names: Young Jung & Luis Garcia
	Project Expectations: What does each group member hope to get out of this project?
	We expect to complete the project while obtaining new knowledge. Learn to pair effectively and to learn from each other. Overall generating real-world practice working with pairs.
	Goals and expectations: Finish the project and do an extension if possible.
	Team strengths: Two heads are better than one. Both have basic understanding of Ruby, time management skills, flexibility, good at asking questions. We are expert Google users.

	How to overcome obstacles: Working together, communicating openly and directly.
	Schedule Expectations (When are we available to work together and individually?): Young : Not available Saturday 8/26 but otherwise available. Luis : Open schedule, not Saturday.
	Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): At least once a day, during available project work hours and after/before class. Use resources like Slack to keep in communication at other times.
	Abilities Expectations (Technical strengths and areas for desired improvement): Young : I want to improve my ability to write code without a specific interaction pattern given and how to break down logic into smaller pieces. Luis : Want to improve ability to write basic, elementary code without referring to notes, improve memorizing basic coding practices.
	Workload Expectations (What features do we each want to work on?): Luis : Learn File I/O Young : same
	Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): Use branching in Github.
	Expectations for giving and receiving feedback: Be polite but honest.
	Agenda to discuss project launch: Whiteboard project
	Split project up
	Ideas:
	Tools:
	Additional Notes: