Skip to content

Latest commit

 

History

History
79 lines (54 loc) · 3.57 KB

DTR.md

File metadata and controls

79 lines (54 loc) · 3.57 KB

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 your learning goals for this project? What drives us in this project?
  • What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
  • How do you communicate best? How do you appreciate receiving communication from others?
  • How would you describe your work style?
  • What are your strengths? How can our strengths complement each other?
  • What’s gone well or poorly in your previous projects?
  • How will we set direction and make decisions as a team?
  • How will we overcome obstacles?
  • What do you need (resources, environment, communication) to do your best work?
  • What scheduling restraints do you have? What are your scheduling preferences?
  • What is your style for giving feedback? Does anything ever hold you back from giving feedback?
  • 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?
  • What tools do you want to use to manage the project?
  • How do you want the group to solve problems when members run into issues with features of the project?
  • How do you know if a project is successful? How can we achieve that as a group?
  • How will we recognize each other's successes and celebrate them?

Any additional questions that you would like to add:

Template for DTR Memo

Project: Book Club

Group Member Names: Ryan McNeil, Ruth Brand

Project Expectations: What does each group member hope to get out of this project?

  • Ryan: Hopes to get a better understanding of ActiveRecord and learning all of the database commands with Rails
  • Ruth: Hopes to get more practice and become faster at doing everything Goals and expectations:

Team strengths:

  • Ryan: Good understanding of ERB and CSS
  • Ruth: Good at asking questions, time-boxing

How to overcome obstacles:

  • We'll use each other as resources, then reach out to cohort/upper mod/ mentors

Schedule Expectations (When are we available to work together and individually?):

  • Generally available to work together before/after school during the week. Available Sunday, and Saturday if needed

Communication Expectations (How and often will we communicate? How do we keep lines of communication open?):

  • Communicate by text, as needed.
  • Open communication while we're working (rubber-ducking, etc)

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

  • Ryan: Good with layouts and good understanding of Rails/MVC, but needs to work on ActiveRecord
  • Ruth: Rails, database, MVC stuff makes sense, but needs to work on layouts

Workload Expectations (What features do we each want to work on?): -Ryan on Index, and Ruth on Book show to begin. Knock out user stories as needed

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests):

  • Use waffle.io for breaking up user stories.
  • Git - always merge each others' pull requests unless directed otherwise

Expectations for giving and receiving feedback:

  • Be open about feedback, before and after project

Agenda to discuss project launch:

  • 10/9 get wireframe and split up work (define deadlines)

Ideas:

Tools:

  • Rails, ActiveRecord, waffle.io, andras.zarovi.cz/sql/demo

Additional Notes: