Skip to content

Instantly share code, notes, and snippets.

@rubyr
Created April 2, 2020 21:58
Show Gist options
  • Save rubyr/e4a27a566baab56e1e2e39467012ea95 to your computer and use it in GitHub Desktop.
Save rubyr/e4a27a566baab56e1e2e39467012ea95 to your computer and use it in GitHub Desktop.

DTR: Define the Relationship

Guiding Questions to Define The Relationship:

Project: Refractor Tractor

Group Member Names: Jeremiah, Edita, Ruby

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?): Edita wants to struggle on the things she doesn't know but ultimately learn and grow as a developer. Jeremiah wants to become a master at pseudocoding and improve his technical language. Ruby wants to get comfortable working with more than one person (they had one partner last mod)

Team strengths & collaboration styles (consider discussing your Pairin qualities here): We all want to do at least one daily check-in to discuss where we're at, what we still need to do, if anything is happening that anyone else needs to know about, etc.

How we can use our strengths to overcome obstacles: Edita is flexible, creative, and open to try whatever. Jeremiah is a "conflict wrangler," compassionate, and a team player. Ruby is good at focusing on problems and seeing the bigger picture.

Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section): Edita is flexible and has a cutoff at 10pm and usually doesn't work on sundays. Jeremiah doesn't really have any off days, but his availability depends on when he wakes up. Additionally, he asks for his team members to have patience with him for the first few days while he gets "into the rhythm." Ruby doesn't work on sundays and has limited availabilities on friday nights. Additionally they are unavailable after 8pm.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?): Daily check ins (depending on the scenario, either a call or a text chat.) Additionally, we'll talk as much as is necessary in case any problems arise.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Edita isn't as strong with the terminal or GitHub but has a good eye for design and layout. Jeremiah wants to improve on vocabulary, but is kind of (sic) good at DOM manipulation. Ruby is good at problem solving and data manipulation, but is still weak in the area of how the data relates to the model.

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

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

Pomodoro Break Schedule: Everyone takes breaks when they think they need to, not on a set schedule.

Expectations for giving and receiving feedback: Be nice, but straightforward -- be patient (especially early!)

Additional Remote Considerations: Background noise might happen- let it be.

Project management tools we will use (GitHub projects or Trello are popular tools): Github Projects

Day 1 Agenda: DTR, read the existing codebase

Additional Notes: Focus on learning SCSS, fetch, jQuery, and webpack!

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