MillsProvosty · September 2, 2019 21:43
diff --git a/gistfile1.txt b/gistfile1.txt
 DTR: Define the Relationship

 Template for DTR Memo
 Project:

 Group Member Names:
 Jori Peterson, Paul Schlattmann, Oscar Bellechaise, Mills Provosty

 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?):
 - Clutch It! 
 - Completion of being able to locate and create events/users.
 - Learn a little more javascript
 - Improve on API consumption 
 - Group Messaging

 Team strengths & collaboration styles (consider discussing your Pairin qualities here):
 - Mills: Communication
 - Paul: Ability to learn Anything. Requires direct communication
 - Jori: Reliable
 - Oscar: Willing to do anything in terms of the project

 Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
 - Mills: Sunday 9:30-2 pm piano lessons, otherwise, time is 100% open. 
 - Jori: not before 8 am
 - Oscar: Wed night is out 
 - Paul: Wed day- Dr. Appt

 General: Please slack

 Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
 -Slack when something changes project
 -Daily Retro at 8:30/Check-ins: Progress, hold-ups, goals for the day, poms, work time expectations.

 Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
 -Stella: Understanding consuming API's, how to make design decisions, prioritize time, best path towards MVP.
 -Mills: More robust tests, dryer code, better at seeing opportunitites for abstraction.

 What features do we each want to work on?
 (come back)

 Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
 Don't merge your own code, commit pattern: test/functionality = a pushed commit. 
 Have template for PR's, super descriptive. 
 All functionality, including model instance/class methods should be tested and passing before push. 

 Expectations for giving and receiving feedback:
 Kind, specific, actionable and timely.
 Be direct.

 Project management tools we will use:
 Github
 Projects board
 Slack

 Day 1 Agenda:
 Set up Repo
 Create Project Board 
 Come up with plan of attack!
	DTR: Define the Relationship

	Template for DTR Memo
	Project:

	Group Member Names:
	Jori Peterson, Paul Schlattmann, Oscar Bellechaise, Mills Provosty

	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?):
	- Clutch It!
	- Completion of being able to locate and create events/users.
	- Learn a little more javascript
	- Improve on API consumption
	- Group Messaging

	Team strengths & collaboration styles (consider discussing your Pairin qualities here):
	- Mills: Communication
	- Paul: Ability to learn Anything. Requires direct communication
	- Jori: Reliable
	- Oscar: Willing to do anything in terms of the project

	Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
	- Mills: Sunday 9:30-2 pm piano lessons, otherwise, time is 100% open.
	- Jori: not before 8 am
	- Oscar: Wed night is out
	- Paul: Wed day- Dr. Appt

	General: Please slack

	Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
	-Slack when something changes project
	-Daily Retro at 8:30/Check-ins: Progress, hold-ups, goals for the day, poms, work time expectations.

	Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
	-Stella: Understanding consuming API's, how to make design decisions, prioritize time, best path towards MVP.
	-Mills: More robust tests, dryer code, better at seeing opportunitites for abstraction.

	What features do we each want to work on?
	(come back)

	Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
	Don't merge your own code, commit pattern: test/functionality = a pushed commit.
	Have template for PR's, super descriptive.
	All functionality, including model instance/class methods should be tested and passing before push.

	Expectations for giving and receiving feedback:
	Kind, specific, actionable and timely.
	Be direct.

	Project management tools we will use:
	Github
	Projects board
	Slack

	Day 1 Agenda:
	Set up Repo
	Create Project Board
	Come up with plan of attack!