Use this template to 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:
Project: Cross Check
Group Member Names: Oscar, Nathan, Tyler
- 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?):
- All of us: Learn how to work on a group project efficiently on GitHub
- Oscar: Better understanding of modules
- Nathan: Implementing modules
- Tyler: Working with a large collection of data to retrieve relevant data
- Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- Whiteboarding and conceptualizing together and working on our own parts for the most part solo.
- Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- During Turing-scheduled work time, work on the project with the group. Maintain work (lesson review, exercises) outside of the project.
- Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
- Daily checkin. Slack direct messages. Honest compromise.
- Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
- Learn from eachother. Better understanding of automation (less hardcoding).
- Workload Expectations (What features do we each want to work on?):
- Fair distribution. Potentially splitting up each iteration.
- Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- Committing frequently. Working on different branches.
- Expectations for giving and receiving feedback:
- Using the comment system on GitHub
- Project management tools we will use:
- GitHub projects Day 1 Agenda:
Additional Notes: