DTR_Memo.md

DTR: Define the Relationship

Use this template to when conducting DTR with your project partners. It's recommended that you copy/paste this template into your own gist each time you conduct a DTR to take notes on the conversation.

Guiding Questions to Define The Relationship:

• What are each of our learning goals for this project? What drives us in this project?

  Increase thinking skills on algorithims. Learn how to work in a team on a coding project, especially with using GitHub together. Learning and getting to the next Module will drive us in this project.

• What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?

  Preference would be pair programming, but since there is July 4th break, we will also divide and conquer.

• How do you communicate best? How do you appreciate receiving communication from others?

  We communicate best in person. We would like to tell each other when we have completed something, come across a problem, etc. More communication is best.

• How would you describe your work style?

  We need time to digest information first before collaborating, but we can also work together to complete tasks faster if need be.

• What are each of our strengths? How can our strengths complement each other?

  We're detail-oriented. This will help in completing tasks that require a lot of focus, like ruby syntax and GitHub commits. We are open to many communication methods.

• What’s gone well or poorly in your previous projects?

  Lack of organization and communication will be a huge obstacle. Making sure we are comfortable with our working relationship.

• How will we set direction and make decisions as a team?

  Always talk to other person first before making a decision. Send each other code when we do something. Add comments.

• How will we overcome obstacles?

  Reach out to other person first to respectfully address and solve problem.

• What do you need (resources, environment, communication) to do your best work?

  It's helpful to be at Turing or some other productive work environment to get work done.

• What scheduling restraints do you have? What are your scheduling preferences?

  Sunday will be our day in person. As well as Friday. We will probably work at afternoon/nights more often.

• What is your style for giving feedback? Does anything ever hold you back from giving feedback?

  Honest feedback is best, since we need to resolve any issues or challenges in an organized and quick fashion.

• What do you identify as being your biggest strength(s) technically, as they relate to this project? Where do you feel you could use improvement in your technical skills, as they relate to this project? How can our team help support you in improving these skills?

  Scott is good at making Tests and methods to solve those tests. Learning the algorithms and learning advanced concepts will be something we can work on.

• What tools do you want to use to manage the project?

  Definitely Github, Slack for communication, and Atom for text editing.

• How do you want the group to solve problems when members run into issues with features of the project?

  We need to Slack the code and work through problems together.

• How do you know if a project is successful? How can we achieve that as a group?

  If we meet Rubric requirements, that is a success for us.

• How will we recognize each other's successes and celebrate them?

  Whenever something works, compliment the other person.

• Any additional questions that you would like to add:

Template for DTR Memo

Project: Battleships

• Group Member Names: Joshua Sherwood and Scott Payton

• 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?): Increase thinking skills on algorithims. Learn how to work in a team on a coding project, especially with using GitHub together. Learning and getting to the next Module will drive us in this project.

• Team strengths & collaboration styles (consider discussing your Pairin qualities here):
  We're detail-oriented. This will help in completing tasks that require a lot of focus, like ruby syntax and GitHub commits. We are open to many communication methods.

• How we can use our strengths to overcome obstacles: Scott is good at making Tests and methods to solve those tests. Learning the algorithms and learning advanced concepts will be something we can work on.

• Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Sunday will be our day in person. As well as Friday. We will probably work at afternoon/nights more often.

• 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 need to Slack the code and work through problems together. More communication is better.

• Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Scott is good at making Tests and methods to solve those tests. Learning the algorithms and learning advanced concepts will be something we can work on.

• Workload Expectations (What features do we each want to work on?): We will do a lot of the work together, but we can also assign individual tasks (and running separate branches) for things we can do seperately.

• Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Using Slack to send code whenever we make a change, and then using GitHub pull request to merge work after we have reviewed it.

• Expectations for giving and receiving feedback: Communicate often. Honest feedback is best, but done respectfully.

• Project management tools we will use: Definitely Github, Slack for communication, and Atom for text editing.

• Day 1 Agenda: Meet for an hour over Slack to review Rubric and get a feel for the project

Additional Notes:

Looks good -- appreciate the level of detail here!