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:
Group Member Names: Olivia Webster and Megan Venetianer
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?): Megan: Get comfortabelt with flex box and JS Olivia: also flex box and JS, and learn best time management strategy for projects. Start feeling more comfortable with the use of vocabulary and explaining things out loud to someone else. Get more specific with questions.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
We both like a combination of working alone and together. We like working through things on our own for a bit and then coming together as a group. Pair programming is useful because you're both workig on the same thing so there will be no unmet remote expectations. DAC might save time and is more useful later at night when we are both home.
How we can use our strengths to overcome obstacles:
We are both strong communicators and we are both invested in the success of the group and other person. Neither of us have huge egos about this and are both willing to approach this project from a humble place. We're both honest and are willing to communicate struggles in a timely way.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
We are both flexible. Willing to work largely a couple hours after class and before class for an hour or so. We are also going to meet on the weekends.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
We will both communicate every day both in person and on slack. If any decision needs to be made we will discuss it before proceeding.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
megan: I pretty organized and detail orientied with code. more comfortable with CSS, flexbox, JS syntax. Olivia: good at problem solving also wants more practice with CSS and JS syntax. pretty solid on HTML.
Workload Expectations (What features do we each want to work on?): The initial HTML and CSS we will do together. Once we have basic set up we will assign different parts of page for each of us to perfect. The JS functionality we will work on together and then assign different specific functionality as the project progresses.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): We will use user stories to make sure our pull requests are pretty equal. We are hoping to learn more about how to deal with work flow tomorrow.
Expectations for giving and receiving feedback:
Honest and specific. It helps to have what we have done right pointed out so that we can refer to those things later.
Project management tools we will use (GitHub projects or Trello are popular tools): We will use GitHub, Trello and Slack.
Day 1 Agenda:
Additional Notes: