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?
- To learn as much JS as possible.
-
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- Bri: I want to balance both. I don't want to lean too much on others' knowledge to the point that I haven't internalized the material. If there's something you know how to do, I hope that I can be the "navigator" so I can learn through struggle.
- Brandy: Collaboration at the beginning, then divide-and-conquer once we have a foundation.
-
How do you communicate best? How do you appreciate receiving communication from others?
- Bri: In person or via text/slack.
- Brandy: Slack
-
How would you describe your work style?
-
Bri: Periods of intense focus with hourly breaks. I can be pretty social if not in a private, quieter space. I work well with music on if working individually.
-
Brandy:
-
-
What are each of our strengths? How can our strengths complement each other?
- Bri: I want to make sure both of our needs are being met (beyond the scope of the project)
-
What’s gone well or poorly in your previous projects?
- Bri: Not committing changes early enough!
-
How will we set direction and make decisions as a team?
- Daily check-ins. 8:30am
-
How will we overcome obstacles?
-
What do you need (resources, environment, communication) to do your best work?
-
Bri: enough sleep! Environment: quiet space
-
Brandy: sleep. verbal communication/thinking through problems/talking through them.
-
-
What scheduling restraints do you have? What are your scheduling preferences?
-
Bri: No restraints, really. I will hopefully be moving so that may affect a weekend. Schedules are important to me -- I want to plan out as much as possible (within reason).
-
Brandy: Get here at 8. Sometimes Thursday night constraints.
-
-
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
- Asking questions.
-
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?
- Brandy: HTML, media queries!
- Bri: CSS -- want to improve on media queries
-
What tools do you want to use to manage the project?
- Trello/Slack
-
How do you want the group to solve problems when members run into issues with features of the project?
Once we get to an hour and we can't figure it out, we contact other person. If they don't know, reach out to Rocks/Mentors/Mod2
-
How do you know if a project is successful? How can we achieve that as a group?
- Brandy: Walking away feeling confident in the JS
- Bri: Getting those advanced beginner objectives complete with 1 or 2 proficient?
-
How will we recognize each other's successes and celebrate them?
We already did!
-
Any additional questions that you would like to add:
Number Guesser
Brandy Mello & Brianna DelValle
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?):
-
Brandy: Walking away feeling confident in the JS we write.
-
Bri: I want to feel better with media queries, and more confident in JS.
-
Pair: Understanding all of the functionality. Meeting the goals on the rubrics (set by Travis)
-
Big goals: appending card and removing cards for winners. More comfort with git workflow.
- We will both be looking out for each other's needs and goals. We both will learn and grow.
- We've already set a boundary for not getting lost in the weeds -- after 1 hour of being stuck, we will check in with each other and upper mod students.
- Checking in for emotional wellbeing.
- We both have a strong interest in the actual learning, not just the completion of the project.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- Brandy has some constraints before 8 am and some Thursdays. Brianna will have some incidental constraints with moving in the next few weeks.
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 have a daily checkin at 8:30 am -- we will plan our attack for the day. We will slack when not together as needed. We will reschedule for 8 am if there was an overnight/late issue.
- Brandy: Strong HTML and media queries. Looking to improve JS everything.
- Bri: Comfort with CSS and git. Want to deepen understanding of git workflow, gain more confidence in writing JS functions.
- Will determine on an as-needed basis. We will build HTML together and go from there.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
- We will walk through branching/github repo sharing/merging/pull requests today.
- We will use coauthored commits when we're working together.
- We will try to push/merge/pulldown near the same time
- Lead with inquiry -- help uncover root of misunderstandings
- Brianna wants to be sure to ask for code review outside of the git workflow -- reach outside to Mod2 Thursday after first checkin. Repeat if necessary.
- Trello, Slack, GitHub
- Together:
- Wireframe
- HTML
Additional Notes:
Really great information here that you've shared in setting up expectations, nice work!