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.
- 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:
- 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?
Project: Refactor Tractor - What's Cookin
Group Member Names: Boone Epstein, Brian Forbes, Cameron Aragon
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?):
Ability to work with other developer's code and strengthening our refactoring skills. Use and have a deeper understanding of divide and conquer work. Better understanding of network request and API's to retrieve data for the program we're building. Understand CSS Sass, inheritance and webpack.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
We're okay with pair programming, but would like to use the divide-and-conquer approaches more so throughout this project. Get practice with using pull-request without knowing what partner has developed before-hand.
How we can use our strengths to overcome obstacles:
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):
Not get together on Sunday's, but everybody is free every other day. Boone has plans from 4-5 on Tuesdays. Boone is an hour ahead from Brian and Cam.
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?):
Check in with each other not only about project, but also on well-being from time to time.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
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:
Every 40 minutes.
Expectations for giving and receiving feedback:
Consistent and open communication, either over zoom in a direct manner or through a slack message.
Additional Remote Considerations:
Project management tools we will use (GitHub projects or Trello are popular tools):
Miro and GitHub Projects
Planning for Sprint:
By Saturday night we should be at the point where testing and classes should be at a finished structure. They should be completed enough to the point where we can start manipulating the data. Be great to have some DOM manipulation working on a working branch. By end of day Thursday we should have no major questions about webpack. Clarify the Data Model prior to any DOM manipulation work.