Skip to content

Instantly share code, notes, and snippets.

@Aeickelman40
Last active July 20, 2020 18:59
Show Gist options
  • Save Aeickelman40/92e90e40a09c112ccc1ec48deaceb78b to your computer and use it in GitHub Desktop.
Save Aeickelman40/92e90e40a09c112ccc1ec48deaceb78b to your computer and use it in GitHub Desktop.

DTR: Define the Relationship

Guiding Questions to Define The Relationship:

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

Figure out postgreSQL, how to deploy to Heroku, backend testing logic, general understanding of backend/frontend relationship.

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

Justin- enthusiastic and bring energy Jeremiah- pairing for a few hours per day especially at the start. Alex- Make sure everyone is in the loop, start pairing, divide after feeling comfortable.

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

Checking via Slack daily, voice call at the beginning of the day just to get everyone on the same page.

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

Justin- creativity, eye for aesthetics. Jeremiah- setting up express felt good. Alex- post/get/delete requests

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

Justin- testing Alex- overcommunication

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

Democratic process, with a backup alternative if the first solution doesn't pan out.

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

Good communication, limited distractions, good music.

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

After 3.5 hours of straight work, have time to step away and recharge. Cut off time around 7pm.

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

GitHub project board, slack for calls, open for tuple.

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

Whenever we have time to go back and refactor, clean up styling, solid fully fleshed out testing suite.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment