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?
Practice JS, get as far in the project possible, BUT make sure each iteration is as good as we can make it.
- What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
Recognize where we think our programming strengths are and be the navigators on those pairs, make sure to pair on the most difficult functionality.
Have a discussion to figure out which type of pair programming works for which feature.
-
How do you communicate best? How do you appreciate receiving communication from others? In person or on Slack. Daily standups 8:40.
-
How would you describe your work style? Deadline. EOD goals.
-
What are each of our strengths? How can our strengths complement each other?
Cody -technical: CSS and HTML, refactoring CSS -personal: Agreeable, driven Allie -technical: breaking down down functions into manageable chunks and guess how long they will take, husband as resource -personal: fulfill commitments, agreeable Vee -technical: TDD, classes and methods, troubleshooting, husband as resource (Vee will own the PM tool) -personal: Time management,
- What’s gone well or poorly in your previous projects?
- What went well: Planning, daily standups, dividing labor,
- What didn't go well: lack of communication, lack of organization
- Stuff we want to try: PR reviews, BEM naming
- How will we set direction and make decisions as a team?
Use PM tool to make sure we see what to accomplish. Make suggestions, reach consensus?
- How will we overcome obstacles?
Leverage our resources. For personal, work with Allison or Jhun, for technical, use rocks and mentors
- What do you need (resources, environment, communication) to do your best work?
Clear idea of how long everyone can work.
- What scheduling restraints do you have? What are your scheduling preferences?
Allie: Can't stay late Wednesday Cody: Might have a few weekday commitments later in the month Vee: Can stay until 7 on any day listed.
Stay late Monday, Tuesday, Friday, no obligation to stay after 7.
- What is your style for giving feedback? Does anything ever hold you back from giving feedback?
We all prefer hard feedback as long as it's not cruel and personal, should be constructive. Appreciations and coaching during standups?
- 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?
Cody -technical skills: CSS and HTML, refactoring CSS -technical tough spots: JS syntax Allie -technical skills: breaking down down functions into manageable chunks and guess how long they will take, husband as resource -technical tough spots: Neatness, CSS positioning Vee -technical skills: TDD, classes and methods, troubleshooting, husband as resource (Vee will own the PM tool) -technical tough spots: CSS grid and flexbox
- What tools do you want to use to manage the project?
github project board
- How do you want the group to solve problems when members run into issues with features of the project?
Pair together, reach out to outside mentors
- How do you know if a project is successful? How can we achieve that as a group?
Knowing all of the key concepts, understanding each other's code. Get through iteration 3.
- How will we recognize each other's successes and celebrate them?
Appreciations during standups, sharing our successes during standup. Cute animal gift at the end of PR.
Any additional questions that you would like to add:
Project:
Group Member Names: Cody, Vee, Allie
- 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?):
Knowing all of the key concepts, understanding each other's code. Get through iteration 3.
- Team strengths & collaboration styles (consider discussing your Pairin qualities here):
Vee: Organization, relationship building, self-assessment Cody: Strategic and Executive Allie: Strategic and cheerleader
- How we can use our strengths to overcome obstacles:
We're all pretty agreeable, so we will hopefully use this to keep from getting personal when things get tough. We also all like having a plan, so going back to the planning board might be options here.
- Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
Allie: Can't stay late Wednesday Cody: Might have a few weekday commitments later in the month Vee: Can stay until 7 on any day listed.
Stay late Monday, Tuesday, Friday, no obligation to stay after 7.
- Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
Team slack, daily standups at 8:45
- Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
Cody -technical skills: CSS and HTML, refactoring CSS -technical tough spots: JS syntax Allie -technical skills: breaking down down functions into manageable chunks and guess how long they will take, husband as resource -technical tough spots: Neatness, CSS positioning Vee -technical skills: TDD, classes and methods, troubleshooting, husband as resource (Vee will own the PM tool) -technical tough spots: CSS grid and flexbox
-
Workload Expectations (What features do we each want to work on?):
-
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
PR reviews - no pushing unless we review. Pair on trounble spots Leverage mentors
- Expectations for giving and receiving feedback:
We all prefer hard feedback as long as it's not cruel and personal, should be constructive. Appreciations and coaching during standups?
- Project management tools we will use (GitHub projects or Trello are popular tools):
Github projects
- Day 1 Agenda:
- Send EOD deliverabler to Eric
- Build HTML tree
- Finish CSS tonight
- Scope out JS for TM
Additional Notes: