megstang · February 11, 2019 21:59
diff --git a/Capstone DTR b/Capstone DTR
 # DTR: Define the Relationship

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






 ### Template for DTR Memo

 Project: Capstone

 Group Member Names: Geoff, Meg, Cole, Ashley

 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?):
 A/C - Learn and master React Native as well as testing for React Native, using expo
 M/G - Use Rails API and push ourselves to use mailers (possibily Twilio - texting), use background workers to optimize speed for user experience, and use caching.
 	
 Team strengths & collaboration styles (consider discussing your Pairin qualities here):
 C - worlds fastest coder
 A - designs and puns 
 M - implementing new ideas
 G - architecture, SRP

 Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
 C - Available any day after class or in the afternoon. Available in the morning if necessary but would prefer not to. Find with remote as well. 
 A - Same as Cole for the most part. Available every day but would prefer not to come in the morning as well. 
 M - Available in the mornings. If I don't go home at lunch to let pups out then I am able to stay after. Otherwise, I will need to go home around 4:00 and then I can come back to work as well. I also don't mind working remotely. I also will be unavailable on Tuesday 2/12 from 11-12.
 G - Appointment on 2/13 at 2:00. Other than that he is free and clear. 

 Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
 We will use slack, or texting. 
 Everyone should have an understanding of what each person is doing in the project. 

 Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
 C/A- React Native and testing 
 G/M - Background workers and caching, becoming more familiar with service oriented programming in Rails

 Workload Expectations (What features do we each want to work on?):
 C/A- Front end, swiping/using animations, and general layout of app
 G/M - Creating endpoints for registering, logging in, saving data, emailing with mailcatchers

 Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): 
 - PR template 
 - Use git pull --rebase origin master
 - waffle
 - figma

 Expectations for giving and receiving feedback:
 Be specific, actionable and kind. Feedback of any form --- in person, slack, doesn't matter for any of us

 Project management tools we will use:
 - waffle
 - figma
 - slack

 Day 1 Agenda: 
 DTR
 Initialize your repositories (don’t write any code just yet!)
 Set up your scrum board and connect them to your repositories (you can have multiple repositories connected to a single Waffle board)
 Each student create your goal for something you would like to learn about the other stack (BE student creates learning goal for something about the FE, and vice versa)
 Normalize on git workflow (we recommend using a “rebase” workflow, as opposed to “merge”, as it is most common on the job) - use a PR template
 Determine MVP (knowing it could change as the project continues)
 Create user stories
 Create wireframes
 Construct schema design
 Decide on rough tech stack

 Additional Notes:
	# DTR: Define the Relationship

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






	### Template for DTR Memo

	Project: Capstone

	Group Member Names: Geoff, Meg, Cole, Ashley

	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?):
	A/C - Learn and master React Native as well as testing for React Native, using expo
	M/G - Use Rails API and push ourselves to use mailers (possibily Twilio - texting), use background workers to optimize speed for user experience, and use caching.

	Team strengths & collaboration styles (consider discussing your Pairin qualities here):
	C - worlds fastest coder
	A - designs and puns
	M - implementing new ideas
	G - architecture, SRP

	Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
	C - Available any day after class or in the afternoon. Available in the morning if necessary but would prefer not to. Find with remote as well.
	A - Same as Cole for the most part. Available every day but would prefer not to come in the morning as well.
	M - Available in the mornings. If I don't go home at lunch to let pups out then I am able to stay after. Otherwise, I will need to go home around 4:00 and then I can come back to work as well. I also don't mind working remotely. I also will be unavailable on Tuesday 2/12 from 11-12.
	G - Appointment on 2/13 at 2:00. Other than that he is free and clear.

	Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
	We will use slack, or texting.
	Everyone should have an understanding of what each person is doing in the project.

	Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
	C/A- React Native and testing
	G/M - Background workers and caching, becoming more familiar with service oriented programming in Rails

	Workload Expectations (What features do we each want to work on?):
	C/A- Front end, swiping/using animations, and general layout of app
	G/M - Creating endpoints for registering, logging in, saving data, emailing with mailcatchers

	Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
	- PR template
	- Use git pull --rebase origin master
	- waffle
	- figma

	Expectations for giving and receiving feedback:
	Be specific, actionable and kind. Feedback of any form --- in person, slack, doesn't matter for any of us

	Project management tools we will use:
	- waffle
	- figma
	- slack

	Day 1 Agenda:
	DTR
	Initialize your repositories (don’t write any code just yet!)
	Set up your scrum board and connect them to your repositories (you can have multiple repositories connected to a single Waffle board)
	Each student create your goal for something you would like to learn about the other stack (BE student creates learning goal for something about the FE, and vice versa)
	Normalize on git workflow (we recommend using a “rebase” workflow, as opposed to “merge”, as it is most common on the job) - use a PR template
	Determine MVP (knowing it could change as the project continues)
	Create user stories
	Create wireframes
	Construct schema design
	Decide on rough tech stack

	Additional Notes: