liambarstad/gist:0d8b84382613ef8e947d3b7b85846976

## gistfile1.txt
DTR: Define the Relationship

Project: ENIGMA
Group Member Names: Liam Barstad, Tim Joo
Project Expectations: What does each group member hope to get out of this project? Both of us want to get more experience learning the nuances of working together in pair programming and getting better with algorithms.
Goals and expectations: In the context of scoring rubric, our goal is to hit 4's across the board but our expectation is to hit 3's across the board. Liam's goal is to have our code readable, accessible, clean, and concise. Tim's goal is to have clean code, his expectation is to having working code.
Team strengths: We have a mix of strengths and we believe that our team strength is that we'll dissect the problems in different ways and analyze different solutions for those problems.
How to overcome obstacles: An emphasis on open communication, leveraging mentors and asking people for help is going to extremely important to overcoming obstacles. Also reviewing prior lesson plans and pooling strengths and resources.
Schedule Expectations (When are we available to work together and individually?): The weekend is committed to individual work. Weekdays after class is time to spend on paired programming and making sure our code is compatible, accessible, and it works.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): Lines of communication will be primary slack and a screen sharing application. Secondary comm will be email text phone. It'll be important to have at least one or two check-ins a day at least over the weekend.
Abilities Expectations (Technical strengths and areas for desired improvement): Areas of desired improvement is refactoring, cleaning up code, making it readable and accessible. Making the code consistently work regardless of input.
Workload Expectations (What features do we each want to work on?): Liam is working on key generator, Tim is working on off set calculator. We're going to figure this out more in detail after pseudocoding the entire project.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): We're going to push version control in one public github account.
Expectations for giving and receiving feedback: Just be upfront.
Agenda to discuss project launch: Our first step is to pseudocode the entire project and then break down deliverables based on the pseudocode. And then, work independently over the weekend. On Monday we will reconvene and put code together. By Wednesday our goal is to have everything working and to refactor the code.
Ideas: Breaking down the pseudocode into smallest parts and finding a solution for each broken down problem.
Tools: We're going to use slack for communication and screenhero / join.me for screen sharing.
Additional Notes: Godspeed to us
	DTR: Define the Relationship

	Project: ENIGMA
	Group Member Names: Liam Barstad, Tim Joo
	Project Expectations: What does each group member hope to get out of this project? Both of us want to get more experience learning the nuances of working together in pair programming and getting better with algorithms.
	Goals and expectations: In the context of scoring rubric, our goal is to hit 4's across the board but our expectation is to hit 3's across the board. Liam's goal is to have our code readable, accessible, clean, and concise. Tim's goal is to have clean code, his expectation is to having working code.
	Team strengths: We have a mix of strengths and we believe that our team strength is that we'll dissect the problems in different ways and analyze different solutions for those problems.
	How to overcome obstacles: An emphasis on open communication, leveraging mentors and asking people for help is going to extremely important to overcoming obstacles. Also reviewing prior lesson plans and pooling strengths and resources.
	Schedule Expectations (When are we available to work together and individually?): The weekend is committed to individual work. Weekdays after class is time to spend on paired programming and making sure our code is compatible, accessible, and it works.
	Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): Lines of communication will be primary slack and a screen sharing application. Secondary comm will be email text phone. It'll be important to have at least one or two check-ins a day at least over the weekend.
	Abilities Expectations (Technical strengths and areas for desired improvement): Areas of desired improvement is refactoring, cleaning up code, making it readable and accessible. Making the code consistently work regardless of input.
	Workload Expectations (What features do we each want to work on?): Liam is working on key generator, Tim is working on off set calculator. We're going to figure this out more in detail after pseudocoding the entire project.
	Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): We're going to push version control in one public github account.
	Expectations for giving and receiving feedback: Just be upfront.
	Agenda to discuss project launch: Our first step is to pseudocode the entire project and then break down deliverables based on the pseudocode. And then, work independently over the weekend. On Monday we will reconvene and put code together. By Wednesday our goal is to have everything working and to refactor the code.
	Ideas: Breaking down the pseudocode into smallest parts and finding a solution for each broken down problem.
	Tools: We're going to use slack for communication and screenhero / join.me for screen sharing.
	Additional Notes: Godspeed to us