trbachmann · December 3, 2018 22:22
diff --git a/Hillary-Tiffany-WheelFortune-DTR b/Hillary-Tiffany-WheelFortune-DTR
 # Project: Wheel of Fortune

 Group Member Names: Hillary Stewart and Tiffany Bachmann

 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?):  
 - Create a working game
 - Test functionality as we work through the project, TDD
 - Properly implement inheritance for our classes
 - Working project to put into code fair
 	
 Team strengths & collaboration styles:  
 - Both like driver navigator, especially when buidling out the initial aspects of the project. Then move into working separately and coming back together for code review
 - Enthusiastic
 - Comfortable working with datasets through different array prototype methods

 How we can use our strengths to overcome obstacles:  
 - We enthusiam to pick each other up, if we are stuggling and feeling stuck
 - Communication to talk through obstacles we hit

 Schedule Expectations (When are we available to work together and individually? What constraints do we have?):  
 - Open to working together during work times and available to work until 6:30pm weekdays at school
 - We'll check in with eachother on Friday to see when we want to meet and what we want to work on over the weekend

 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 eachother if we aren't together at school, otherwise touch base in person. Or if the other person is busy send a quick slack message about what we want to dicuss so we don't lose the thought/idea.

 Abilities & Growth Expectations (Technical strengths and areas for desired improvement):  
 - Better at testing
 - Better at working with multiple classes 
 - Ensuring we're breaking out functionality into different classes

 Workload Expectations (What features do we each want to work on?):  
 - Both open and unbiases on which features we like best

 Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): 
 - Use project tab and issues tab in GitHub to track our progress

 Expectations for giving and receiving feedback:  
 - Communicate and check in with eachother daily

 Project management tools we will use:  
 -GitHub project and issues tabs
	# Project: Wheel of Fortune

	Group Member Names: Hillary Stewart and Tiffany Bachmann

	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?):
	- Create a working game
	- Test functionality as we work through the project, TDD
	- Properly implement inheritance for our classes
	- Working project to put into code fair

	Team strengths & collaboration styles:
	- Both like driver navigator, especially when buidling out the initial aspects of the project. Then move into working separately and coming back together for code review
	- Enthusiastic
	- Comfortable working with datasets through different array prototype methods

	How we can use our strengths to overcome obstacles:
	- We enthusiam to pick each other up, if we are stuggling and feeling stuck
	- Communication to talk through obstacles we hit

	Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
	- Open to working together during work times and available to work until 6:30pm weekdays at school
	- We'll check in with eachother on Friday to see when we want to meet and what we want to work on over the weekend

	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 eachother if we aren't together at school, otherwise touch base in person. Or if the other person is busy send a quick slack message about what we want to dicuss so we don't lose the thought/idea.

	Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
	- Better at testing
	- Better at working with multiple classes
	- Ensuring we're breaking out functionality into different classes

	Workload Expectations (What features do we each want to work on?):
	- Both open and unbiases on which features we like best

	Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
	- Use project tab and issues tab in GitHub to track our progress

	Expectations for giving and receiving feedback:
	- Communicate and check in with eachother daily

	Project management tools we will use:
	-GitHub project and issues tabs