Skip to content

Instantly share code, notes, and snippets.

@emackinnon1
Created June 29, 2020 21:18
Show Gist options
  • Save emackinnon1/2d14dacdb0e168de1725b53cb176fab9 to your computer and use it in GitHub Desktop.
Save emackinnon1/2d14dacdb0e168de1725b53cb176fab9 to your computer and use it in GitHub Desktop.
# DTR: Define the Relationship
Use this template 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?
* 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 each of our 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:
### Remote Work Considerations During the COVID-19 Quarantine
* What does remote focus look like for you? (headphones, distractions minimized (tv, family stuff, etc), video on)
* When working from the same place where you live, life can get in the way. What are some potential life things that could interfere with your ability to focus, and what plan can we come up with to approach those issues? (Examples: my kids, my dog, my partner, etc.)
* If we encounter issues such as power outages, Zoom difficulties, or bad wifi, what backup plans can we have in place? (This could have answers like asking a neighbor to borrow wifi, using cellphone hotspot for internet, switching to slack or skype.
* Pomodoro breaks are especially important for remote work and doubly so for quarantine. What should our Pom cadence look like? How will hold ourselves accountable?
* Quarantine is tough, so it’s important to make note of our mental/emotional state when working with others. How can we make space to check in on each other’s well being, in addition to the work that needs to be done?
### Template for DTR Memo
Project:
Crate.
Group Member Names:
Kelsha D, Ben F, Brian G, Ally J, Elliot M
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?):
Getting more familiar with the agile process, redux, express, node.js, working with an existing codebase/open source project.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
For collaboration style on this project, we will plan on group calls to get familiar with the new techs and then implement divide and conquer.
How we can use our strengths to overcome obstacles:
Can lean on each other's technical experience to meet the goals of the project.
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):
Kelsha: Thursday evenings, and saturday mornings has stuff
Brian: Lunch time off, 10:30pm - 5am sleepy time.
Ally: Prefers cut off around dinner time, lunch off, half day on the weekend at least off
Ben: Start time after 9am, off from 4-6pm (flexible), likes being on from 6-9, lunches off
Elliot: Twerk out for an hour (flexible), lunch off, half day on the weekend at least off
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?):
Utilize the slack channel. During agreed-upon work times, we expect group members to be responsive on slack.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
Getting more mofortable with node.js and express and redux.
Workload Expectations (What features do we each want to work on?):
We are assigned style track so we will work on implementing those features. Frontend people work on frontend stuff and backend people work on the backend.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
We will try implementing the slack-github integration. Set up a minimum number of approvals for PR. Will also implement CI. If we run into a problem,
we will ask our group members/others for help after 2 POMs. We will also use the git rebase workflow. Implement PR template, close issues.
Pomodoro Break Schedule:
We will use a timer on group calls.
Expectations for giving and receiving feedback:
Be direct and actionable. Possibly have smaller retros in the evenings?
Additional Remote Considerations:
Occasional problems for ben, barky doggies for Kelsha.
Project management tools we will use (GitHub projects or Trello are popular tools):
Github projects, slack-github integration.
Day 1 Agenda:
Fork repo and add all collaborators. Familiarize ourselves with the code. Get app working on our local machines.
Additional Notes:
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment