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.
- Corey Carter
- Judith Pillado
- Saryn Mooney
- Travis McKinstry
- What are each of our learning goals for this project? What drives us in this project?
-Judith: namespacing
-Saryn: namespacing, practice with users/admin, each person understanding what's happening with each step
-Travis: understand concepts, not just finishing project
-Corey: authentication, active record
* What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
-Judith: Important to divide/conquer, project is long. Don't have to finish, but divide/conquer or pairing.
-Corey: felxible, pairing works.
-Saryn: similar to Corey, can pair, can divide later. Support each other if get stuck
-
How do you communicate best? How do you appreciate receiving communication from others?
-Slack, GitHub (clear with PR, comments, etc.), Corey is a night owl, ping at any time. Travis is on slack all the time, same with Saryn.
-Be mindful of being controlling (extroverts vs introverts). Communicate clear. -
How would you describe your work style?
-Saryn: good at just 'jumping in' and 'failing'.
-Corey: Highy variable. Can stay up all night, can't sleep if can't get it done. But also super flexible.
-Judith: Work best throughout the day. If you're noticing that you have to repeat things to me, time to call it for the day. Usually done by 9PM MST.
-Travis: Any time during the day (as long as I'm not in the gym) -
What are each of our strengths? How can our strengths complement each other?
-Judith: Already did this project, can be organized (won't make project board!)
-Corey: vision (big picture; controllers, for example), super determined.
-Saryn: Flexible, can jump in and do whatever. Organization, keeping big picture.
-Travis: Ruby and rails (separately). -
What’s gone well or poorly in your previous projects?
-Judith: people being too controlling. Personality differences. -
How will we set direction and make decisions as a team?
-Corey: Very important to 'white-board' first. So, brainstorm general design, THEN do. -
How will we overcome obstacles?
-Judith: Communication. Went through unproductive struggle a lot and it was difficult reaching out. Remember; this isn't part of promotion, if we need to take time to understanding something or review, that's fair. -
What do you need (resources, environment, communication) to do your best work?
-Judith: eats dinner right after class, try to communicate through GitHub. -
What scheduling restraints do you have? What are your scheduling preferences?
-Judith: 1 hour ahead of mountain time, meaning she's out by 8PM, also not available 5-6PM MST.
-Corey, Saryn: able to work right after class (after a POM). Between 4-5PM, group chat; talk about yesterday, what areas are challenging, set goals for the day. -
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
-Corey: if you notice me talking a lot or interrupting, PLEASE tell me, I promise I will do better. I don't do it on purpose. -
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?
-Travis: Ruby and Rails (some of active record).
-Corey: RUBY.
-Judith: Comfortable with MVC.
-Saryn: Testing, difference between modle and feature testing. -
What tools do you want to use to manage the project?
-Github, slack, GitHub projects (by user story).
-
How do you want the group to solve problems when members run into issues with features of the project?
-Raise 'issues' on GitHub -
How do you know if a project is successful? How can we achieve that as a group?
-Success is: Each of us can explain the user stories that we've accomplished. Not necessarily how far we get, but being able to explain the user story's that we do finish. -
How will we recognize each other's successes and celebrate them?
-In the moment, 'thank you', gratefulness, putting forth our best efforts.
Any additional questions that you would like to add:
- 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 affect your ability to focus, and what plan can we come up with to approach those moments?
- 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?
Remember, quarantine is tough. Try to be flexible, accomodate who needs it. Speak up for your needs. Number one priority is to learn! Check in with each other as humans, not just as coders. WE ARE FAMILY
Commits: Do what's comfortable
Pull Requests:
Feature being added