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?
- Strengthen of skills or learning new skills
- What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- Pair programming, empathetic collaboration style.
- How do you communicate best? How do you appreciate receiving communication from others?
- Regular check-ins, open lines of communication.
- How would you describe your work style?
- Cooperative
- What are each of our strengths? How can our strengths complement each other?
- Mandy:Methodical, roadmap and direction
- Joel: Diving-in, tackling larger issues
- What’s gone well or poorly in your previous projects?
- Difficulty time-blocking
- How will we set direction and make decisions as a team?
- Discussions and regular check-ins
- How will we overcome obstacles?
- Discussing and breaking-down pieces.
- What do you need (resources, environment, communication) to do your best work?
- Distraction-free space. Sporadic breaks.
- What scheduling restraints do you have? What are your scheduling preferences?
- Tuesday Night this week, we will meet and work in the afternoon.
- What is your style for giving feedback? Does anything ever hold you back from giving feedback?
- Aim for an environment open to 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?
- Willingness to jump in and grit through some struggles.
- What tools do you want to use to manage the project?
- Trello to break down tasks
- How do you want the group to solve problems when members run into issues with features of the project?
- Talk to each other, discuss.
- How do you know if a project is successful? How can we achieve that as a group?
- Did we learn from the project.
- How will we recognize each other's successes and celebrate them?
- Talking
- Any additional questions that you would like to add:
- None
- 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?):
- Top openly communicate To take away from tangible lessons
- Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- Empathetic and communicative Interested in learning as our primary goal, curiosity
- How we can use our strengths to overcome obstacles:
- We’ll communicate well, and be willing to dig into problems
- Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- Work during open sessions, keep channels of communication open. Personal development work in the evenings.
- Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
- Morning check in, generally open lines.
- Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
- Joel: CSS
- Mandy: CSS & Functions
- Workload Expectations (What features do we each want to work on?):
- Try evenly divide work, and work in tandem.
- Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- Communicate if we individually pick up new components, check-ins to ensure we’re in sync. Potentially to be refined as we get into cooperative GitHub development.
- Expectations for giving and receiving feedback:
- Deliver feedback in open-discussion format during check-ins.
- Project management tools we will use (GitHub projects or Trello are popular tools):
- Trello
- Day 1 Agenda:
- Wireframe
- Time-blocking & Trello structure
- Additional Notes:
- None.