Skip to content

Latest commit

 

History

History
62 lines (61 loc) · 3.52 KB

DTR.md

File metadata and controls

62 lines (61 loc) · 3.52 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?
    • APIs
    • Design organization, specifically pre-planning.
    • Group hugs!
  • What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
    • Group/Paired work, not necessarily strong driver/navigator.
    • Mixed programming grouping.
    • Core code should be entire group.
    • Possible split into pairs for project "sides"
  • How do you communicate best? How do you appreciate receiving communication from others?
    • Slack, NO EMAILS
    • over-communicate
    • Sign-off with ALL of your work for the day.
    • Full group check-ins daily
    • Look into Tupple
    • Scheduled group time.
  • How would you describe your work style/ strengths? How can our strengths complement each other?
    • Molly throws things at the wall, and SQL GOD!@!!
    • Lawrence is hard headed but might have something behind the skull. Happy to look through docs to find the active record way.
    • Aliya work now, beautify later. Good with rails and SQL.
    • Solo start strong, may struggle without production. Good SQL. Strong collaboration.
  • What's gone well or poorly in your previous projects?
    • Communication without consequence.
    • Everyone understanding before the rubric.
    • Learning is what we are in school for.
    • Refactor a strong 3 before moving to extensions.
  • How will we set direction and make decisions as a team?
    • Group discussions and check-ins.
    • Let others know before you move into a new area.
    • We are all wearing our big person pants.
  • How will we overcome obstacles?
    • Light the beacon, call the coders.
    • The teachers can be reached.
  • What do you need (resources, environment, communication) to do your best work?
    • Aliya requires silence.
    • Set expectations for our time.
  • What scheduling restraints do you have? What are your scheduling preferences?
    • 8:00 - 8:00 MT, Sundays for self care -- Aliya
    • 9:00 - 9:00 MT, Friday 6:00 sign off for self care -- Sid
    • 8:00 - 8/9:00 MT, Mornings for community work. Morning off on Weekend -- Molly
    • 8:00 - 9:00 MT, Afternoons on weekend. -- Lawrence
  • What is your style for giving feedback? Does anything ever hold you back from giving feedback?
    • Code focused feedback.
    • Ask why a path was used, give alternatives.
    • Honesty and kindness.
    • Comment on the lines of code or provide an example with the 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?
    • Joins, share and comment.
    • Activerecord feedback, this isn't your average everyday confused.
    • Workshop on Activerecord you've written that you are proud of or wish never to be seen.
  • What tools do you want to use to manage the project?
    • Projects section of github. Pull request 'closes #3' on pull request.
  • How do you know if a project is successful? How can we achieve that as a group?
    • We know more then than we do now.
  • How will we recognize each other's successes and celebrate them?
    • Celebrate in pull request reviews.
    • Snaps in our group slack. Any additional questions that you would like to add: