chrisdbasham317 · July 3, 2019 15:35 · allisonreusinger · Jul 3, 2019
diff --git a/number_guesser_DTR1.txt b/number_guesser_DTR1.txt
 Project: Number Guesser

 Group Member Names: Eric Meldrum and Chris Basham

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

  Chris hopes to develop his skills in Javascript and media queries with this project. Eric has the same goals with Javascript   and media queries. We as a team hope to acheive a product that rates "Proficient" on the rubric. We want to also set a         deadline of completing phase 2 by next Tuesday night. We plan to utilize the rubric to gauge our success as a team.
  
 Team strengths & collaboration styles (consider discussing your Pairin qualities here):
  Chris Strengths:
    -Is a very objective/analytical thinker. Really explores concepts until understanding is acheived.
    -Has a fair amount of leadership/followership experience.
    -Chris learns new concepts best by doing them. He is not a multitasker, so tasks/conversations will need to be 
 focused/structured.
  
  Eric Strengths:
    -Flexibility in regards to team roles. He can operate as a supporter or a leader given the situation.
    -Big Picture Thinker: He is able to view the direction of a project as a whole.
    -Collaboration style: Eric is a vocal collaborator, he does well talking concepts through.
    -Eric is also not a multitasker. This will help to structure conversations for both team members.

 How we can use our strengths to overcome obstacles:
    -Chris can use his strengths to focus on the details of the project, and Eric will play on his strengths to keep the project moving in a successful vector.

 Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
  We are going to commit to do working lunches. We will work everyday after school until 1730hrs. Over the 4 day weekend we are commiting to working together in person at least once, but we are going to verify our schedules and re-evaluate for more time. Remote work is going to be completed nightly based on assigned tasks. We our going to be bound by commute time during the school week, as Chris is traveling from Colorado Springs.

 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 be communicating daily, and updating eachother with current task work/task accomplishment. We will make decisions based on discussion we have regarding what we as individuals feel is most beneficial for the project, and hammer out best practices based on those ideas.

 Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
  Semantic HTML, clean/concise HTML are technical strengths for the team. Both members hope to improve technical skills in Javascript and media queries. Both members have some experience with Javascript syntax.

 Workload Expectations (What features do we each want to work on?):
  As group we will accomplish the wire frame, and creating our semantic HTML markup. We have a deadline of tomorrow evening for semantic HTML completion. We will discuss this again after completing that and divide the CSS workload w/ media queries and JavaScript.
 Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
  We will revisit this after the lesson on Git workflow.
 Expectations for giving and receiving feedback:
  We are going have scheduled "retros", the first one will be tomorrow after completion of our HTML markup. The next retro will be scheduled at the end of each previous retro.
 Project management tools we will use:
  Github and conveyor belt are the tools we plan to utilize. 
 Day 1 Agenda:
  Wire-frame, begin HTML
 Additional Notes:
	Project: Number Guesser

	Group Member Names: Eric Meldrum and Chris Basham

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

	Chris hopes to develop his skills in Javascript and media queries with this project. Eric has the same goals with Javascript and media queries. We as a team hope to acheive a product that rates "Proficient" on the rubric. We want to also set a deadline of completing phase 2 by next Tuesday night. We plan to utilize the rubric to gauge our success as a team.

	Team strengths & collaboration styles (consider discussing your Pairin qualities here):
	Chris Strengths:
	-Is a very objective/analytical thinker. Really explores concepts until understanding is acheived.
	-Has a fair amount of leadership/followership experience.
	-Chris learns new concepts best by doing them. He is not a multitasker, so tasks/conversations will need to be
	focused/structured.

	Eric Strengths:
	-Flexibility in regards to team roles. He can operate as a supporter or a leader given the situation.
	-Big Picture Thinker: He is able to view the direction of a project as a whole.
	-Collaboration style: Eric is a vocal collaborator, he does well talking concepts through.
	-Eric is also not a multitasker. This will help to structure conversations for both team members.

	How we can use our strengths to overcome obstacles:
	-Chris can use his strengths to focus on the details of the project, and Eric will play on his strengths to keep the project moving in a successful vector.

	Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
	We are going to commit to do working lunches. We will work everyday after school until 1730hrs. Over the 4 day weekend we are commiting to working together in person at least once, but we are going to verify our schedules and re-evaluate for more time. Remote work is going to be completed nightly based on assigned tasks. We our going to be bound by commute time during the school week, as Chris is traveling from Colorado Springs.

	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 be communicating daily, and updating eachother with current task work/task accomplishment. We will make decisions based on discussion we have regarding what we as individuals feel is most beneficial for the project, and hammer out best practices based on those ideas.

	Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
	Semantic HTML, clean/concise HTML are technical strengths for the team. Both members hope to improve technical skills in Javascript and media queries. Both members have some experience with Javascript syntax.

	Workload Expectations (What features do we each want to work on?):
	As group we will accomplish the wire frame, and creating our semantic HTML markup. We have a deadline of tomorrow evening for semantic HTML completion. We will discuss this again after completing that and divide the CSS workload w/ media queries and JavaScript.
	Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
	We will revisit this after the lesson on Git workflow.
	Expectations for giving and receiving feedback:
	We are going have scheduled "retros", the first one will be tomorrow after completion of our HTML markup. The next retro will be scheduled at the end of each previous retro.
	Project management tools we will use:
	Github and conveyor belt are the tools we plan to utilize.
	Day 1 Agenda:
	Wire-frame, begin HTML
	Additional Notes: