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: Intention Timer
Group Member Names: Collie Kallery, Kyle Wong
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?): Collie: Get good review from the project on fuzzy foundational concepts. Employ new concepts. Kyle: Get more comfortable with JS. DRY-er CSS and JS. Planning ahead.
Team strengths & collaboration styles (consider discussing your Pairin qualities here): Collie: Works well in groups. Would rather work together than independently. Doesn't do great with divide and conquer. Kyle: Works well in groups. Also would like to work together rather than independently. Communication.
How we can use our strengths to overcome obstacles: Working together will allow us to use two heads rather than one at a time. Communicate during moments of confusion rather than silently struggle on our own.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Open from 7am - 6:30pm. Can change depending.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): Slack first then phone. Open and honest communication.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Collie: Since I've been through mod 1 I have done a similar project to this. Strengths in HTML and CSS as well as basic JS. Improve in JS. Kyle: Feel comfortable with HTML and CSS. Want to be able to write JS functions from scratch (i.e. not looking at examples).
Workload Expectations (What features do we each want to work on?): Work together on all aspects of the project rather than divide and conquer. We both want to be involved in all parts of the project.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Git should be used as frequently as possible. Sending small and frequent commits. This way, we can keep track of our work more closely and ensure our progress is in the right direction. If we do end up working separately at all, Code Reviews should look very closely at the code before hitting submit to ensure that both of us fully understand the code that is being used.
Expectations for giving and receiving feedback: Being as open and honest as possible while staying civil and respectful.
Project management tools we will use (GitHub projects or Trello are popular tools): We are using Trello to manage the project workflow.
Day 1 Agenda: DTR complete Trello assignments
Additional Notes: