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: Futbol
Group Member Names: Colin A., Mike H, Ana P.
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?):
-
Colin: a much better understanding of OOP interaction
-
Mike: better understanding of hashes
-
Ana: working collaboratively and being able to stand on my own two feet
-
Team: Complete a passing project and each member understands/made progress on individual goals, better understanding of team git flow
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- Colin: empowering people, logic, collaboratively planning
- Mike: coming up with creative solutions to various scenarios
- Ana: reflecting on team progress, following direction
How we can use our strengths to overcome obstacles:
- Being aware of each other's strengths/weaknesses, we can complement each other, and work as a team to overcome those obstacles
- Explicitly asking members what problems they are having
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- Colin: Open schedule most days, Sat: work 11-7
- Mike: Open schedule most days, Sun: noon to end of day not available, with a caveat
- Ana: Open schedule
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
- Always check-in in the mornings, face-to-face or Slack
- Accomplishments, Problems, Daily Goals
- Utilize screenshots
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
- Colin: OOP, social dynamics
- Mike: familiarity with hashes, git collaboration
- Ana: utilizing my resources when stuck
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- Kanban
- Youtube videos
- SimpleCov
- Review iterations ahead of time
Expectations for giving and receiving feedback:
- Assume positive intent
- Give coaching guidance, not answers
- Keep asking questions if you don't uderstand
Project management tools we will use (GitHub projects or Trello are popular tools):
- GitHub project board? or Kanban?
Day 1 Agenda:
- First day - Monday Slack call (late morning)
- Collectively get a sense of what to expect
- GitHub project board to break it down
Additional Notes: Dummy File - don't just copy the first 15 lines, create more unique data sets Review all iterations both individually
Had to create a separate gist with our already filled out DTR, because of the switch to the instructor-made repo.