trbachmann · December 17, 2018 21:51
diff --git a/national-parks-dtr b/national-parks-dtr
 # Project: Whateverly - National Parks

 Group Member Names:  
 * Adam Niedzwiecki
 * Karin Ohman
 * 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 an application where users can find National Parks information in an easy manner so they can spend more time going to the parks . 
 * Knowledge of React 
 * Continue to build on knowledge of OOP 
 * Sucessful presentation of app, in preparation of future demo opportunities

 Team strengths & collaboration styles:  
 * Group members are all flexible in communication styles and willing to adjust workflow accordingly
 * Prior work expereince on past project (TB and KO)
 * Group members feel confident with OOP

 How we can use our strengths to overcome obstacles:  
 * As a group we plan to have open lines of communication and adjust work styles/timing etc. based on project needs

 Schedule Expectations (When are we available to work together and individually? What constraints do we have?):  
 * During the first week, we plan to have morning checkins before lecture starts
 * Will work together during alloted work-time
 * Flexible over break to get together

 Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):  
 * Will check in on class days before lecture
 * When a member runs into issues when working individually, will slack the other two for help or let them know they are stuck and will work on again when we are together . 
 * Stay on top of issues and pull requests in GitHub

 Abilities & Growth Expectations (Technical strengths and areas for desired improvement):  
 * Knowledge of React 
 * Continue to build on knowledge of OOP
 * Knowledge of testing React with Jest

 Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):  
 * Utilize GitHub issues to track work
 * If a member gets stuck, send slack message to others for help, make notes in issues about how far they got

 Expectations for giving and receiving feedback:
 * Keep open communication between members
 * Daily checkin in the morning

 Project management tools we will use:
 * GitHub Issues

 Day 1 Agenda:
 * Wireframe user stories
 * DTR 
 * Setup Repo
 * Start putting user stories in GitHub issues
	# Project: Whateverly - National Parks

	Group Member Names:
	* Adam Niedzwiecki
	* Karin Ohman
	* 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 an application where users can find National Parks information in an easy manner so they can spend more time going to the parks .
	* Knowledge of React
	* Continue to build on knowledge of OOP
	* Sucessful presentation of app, in preparation of future demo opportunities

	Team strengths & collaboration styles:
	* Group members are all flexible in communication styles and willing to adjust workflow accordingly
	* Prior work expereince on past project (TB and KO)
	* Group members feel confident with OOP

	How we can use our strengths to overcome obstacles:
	* As a group we plan to have open lines of communication and adjust work styles/timing etc. based on project needs

	Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
	* During the first week, we plan to have morning checkins before lecture starts
	* Will work together during alloted work-time
	* Flexible over break to get together

	Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
	* Will check in on class days before lecture
	* When a member runs into issues when working individually, will slack the other two for help or let them know they are stuck and will work on again when we are together .
	* Stay on top of issues and pull requests in GitHub

	Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
	* Knowledge of React
	* Continue to build on knowledge of OOP
	* Knowledge of testing React with Jest

	Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
	* Utilize GitHub issues to track work
	* If a member gets stuck, send slack message to others for help, make notes in issues about how far they got

	Expectations for giving and receiving feedback:
	* Keep open communication between members
	* Daily checkin in the morning

	Project management tools we will use:
	* GitHub Issues

	Day 1 Agenda:
	* Wireframe user stories
	* DTR
	* Setup Repo
	* Start putting user stories in GitHub issues