# DTR: Define the Relationship

## Project: Game Time

### Group Member Names:Chris Lane, Jon O'Drobinak, Alyssa Lundgren

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

 - Get as far as we can, shoot to finish every iteration (want to do animation and AI player extensions)
 - Last day before the project due to refactor and tighten - what we turn in should be tight
 - Combo of paired and individual programming
 - Clear, honest communication and expectations
 - Morning check-in
 - Everyone can explain every bit of code
 - Open to areas of improvement
 - Help each other out of rabbit holes and ask for help
 - Share and celebrate the wins!!!
 - Keep a healthy perspective
 - GOAL: buttoned up by 4pm the day before it's due

#### Team strengths & collaboration styles (consider discussing your Pairin qualities here):

 - Jon - open to suggestions
 - We are a TEAM. Let's do it together. Wins should be shared and struggles should be addressed.
 - Let's stay focused on the code.
 - We all want the experience of the code.

#### How we can use our strengths to overcome obstacles:

 - Communication
 - Collaboration
 - Asking for help

#### Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

 - Our first priority is school.
 - Let's have a game plan in person.
 - Communicate disruptions early so we can address.
 - Alyssa Red Rocks Norah Jones Tuesday (7/16/19)
 - We all want to do well on assessments

#### Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

 - Early and often
 - Morning check-is
 - If you put up a pull request message everyone rigth away
 - If you merge a pull request message everyone right away
 - DON'T SELF MERGE.
 - No pull requests after 8pm
 - Slack
 - Merge conflicts - deal with them locally, larger things together

#### Abilities & Growth Expectations (Technical strengths and areas for desired improvement):

 - Cleaner functions
 - Chaining
 - Cut the fat
 - CodeWars
 - jsFun
 - Each experience the code

#### Workload Expectations (What features do we each want to work on?):

 - Animation
 - jsCharts
 - SRP
 - Clean functional classes
 - Writing the damn code

#### Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

 - Trillo - Chris to get us setup
 - Morning check-is
 - If you put up a pull request message everyone rigth away
 - If you merge a pull request message everyone right away
 - DON'T SELF MERGE.
 - No pull requests after 8pm
 - Small atomic commits
 - PRs for template-able things or once we gain a piece of functionality
 - Refactor iteratively throughout the process rather than all at the end

#### Expectations for giving and receiving feedback:

 - Let's laugh.
 - Honest and kind
 - Friends too.

Project management tools we will use: Trillo

Day 1 Agenda: DTR, whiteboard, clone and set new origin