TomatilloDTR.md

DTR: Define the Relationship

Project: Rancid Tomatillo

Group Member Names: Caleb, Kim and Roger

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

Caleb: Understand the use of redux. Kim: Get comfy with redux. Roger:

Team strengths & collaboration styles:

Strengths: Collaboration style: Paired programming to setup the base. Divide and Conquer to implement features.

How we can use our strengths to overcome obstacles:

Schedule Expectations:

Caleb: Meetups. Kim: Meetups. Roger:

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

Open, straight forward, listen and positive feedback.

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

DRY code base, clean design and not smelly.

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

Everything.

Workflow Expectations:

Follow trello board, consistant code review and use of PR template.

Expectations for giving and receiving feedback:

Open to feedback always. Deliver with empathy in mind.

Project management tools we will use:

Trello

Signs of unproductive struggles:

Caleb: Trying to do more than whats needed before finishing whats needed. Kim: Taking tooooooo long a POM :( Seeking a quick answer vs learning the answer. Distracted (darn internet and its things). Roger: