CHaiz15 · December 2, 2019 22:54
diff --git a/whatsCookinDTR b/whatsCookinDTR
 # DTR: Whats cookin

 ### Guiding Questions to Define The Relationship:

 * What are each of our learning goals for this project? What drives us in this project?
 Caleb: Successfully using array prototype methods. 
 Greg: Learn ES6 syntax.
 Drive: Ability to successfully move on. Gain knowledge.
 * What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
 Pair: beginning, hard points.
 DnC: Once we are able to define specififc functionality to work on.
 * How do you communicate best? How do you appreciate receiving communication from others?
 Face to face and slack. Honest, straight forward, timely.
 * How would you describe your work style?
 Hard work, pom, repeat.
 * What are each of our strengths? How can our strengths complement each other?
 Caleb: Grasp concepts well with mind.
 Greg: Creative (no prompts = yay!)
 * What’s gone well or poorly in your previous projects?
 Well: Re-dtr, define goals.
 Poor: Lots of DnC = a little confusing.
 * How will we set direction and make decisions as a team?
 Project board and re-dtr.
 * How will we overcome obstacles?
 Positive mindset, googles help, ask fellow students, ask rocks, ask mentors.
 * What do you need (resources, environment, communication) to do your best work?
 Chill environment, google, friends to ask.
 * What scheduling restraints do you have? What are your scheduling preferences?
 Caleb: Nothing. Don't get stuck at turing.
 Greg: Apt at 1pm on tuesday. 
 * What is your style for giving feedback? Does anything ever hold you back from giving feedback?
 Straightforward and positive. Nothing held back.
 * 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?
 Caleb: Functions. Work on thinking of TDD tests.
 Greg: Get things working well. Work on Planning.
 * What tools do you want to use to manage the project?
 Trello
 * How do you want the group to solve problems when members run into issues with features of the project?
 Pair, then look for further help. Switch task.
 * How do you know if a project is successful? How can we achieve that as a group?
 We have grasp of the learning goals and our project functions satisfactry to instructors standards.
 * How will we recognize each other's successes and celebrate them?
 Snaps, functionality, jazz hands, high fives, positive remarks. Hype music constantly in the background.

 Any additional questions that you would like to add:
	# DTR: Whats cookin

	### Guiding Questions to Define The Relationship:

	* What are each of our learning goals for this project? What drives us in this project?
	Caleb: Successfully using array prototype methods.
	Greg: Learn ES6 syntax.
	Drive: Ability to successfully move on. Gain knowledge.
	* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
	Pair: beginning, hard points.
	DnC: Once we are able to define specififc functionality to work on.
	* How do you communicate best? How do you appreciate receiving communication from others?
	Face to face and slack. Honest, straight forward, timely.
	* How would you describe your work style?
	Hard work, pom, repeat.
	* What are each of our strengths? How can our strengths complement each other?
	Caleb: Grasp concepts well with mind.
	Greg: Creative (no prompts = yay!)
	* What’s gone well or poorly in your previous projects?
	Well: Re-dtr, define goals.
	Poor: Lots of DnC = a little confusing.
	* How will we set direction and make decisions as a team?
	Project board and re-dtr.
	* How will we overcome obstacles?
	Positive mindset, googles help, ask fellow students, ask rocks, ask mentors.
	* What do you need (resources, environment, communication) to do your best work?
	Chill environment, google, friends to ask.
	* What scheduling restraints do you have? What are your scheduling preferences?
	Caleb: Nothing. Don't get stuck at turing.
	Greg: Apt at 1pm on tuesday.
	* What is your style for giving feedback? Does anything ever hold you back from giving feedback?
	Straightforward and positive. Nothing held back.
	* 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?
	Caleb: Functions. Work on thinking of TDD tests.
	Greg: Get things working well. Work on Planning.
	* What tools do you want to use to manage the project?
	Trello
	* How do you want the group to solve problems when members run into issues with features of the project?
	Pair, then look for further help. Switch task.
	* How do you know if a project is successful? How can we achieve that as a group?
	We have grasp of the learning goals and our project functions satisfactry to instructors standards.
	* How will we recognize each other's successes and celebrate them?
	Snaps, functionality, jazz hands, high fives, positive remarks. Hype music constantly in the background.

	Any additional questions that you would like to add: