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?
- Learn more things. Expand upon knowledge of JavaScript. Work/improve on technical vocab so when we are discussing the code we are using the correct vocabulary. What habits have we each built that we can share with each other. Drive is getting a 4.
- What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- We aren't too sure about the difference between the two - but we want to make sure either approach is still collaborative. Rachael likes to take 5 minutes before group convo. Carlos to work abstractly then come back in and execute. Listing everything out via brainstorm. Checklist with the tasks. Order and a story approach before diving into the code.
- How do you communicate best? How do you appreciate receiving communication from others?
- Carlos - verbal. Receiving - doesn't require "sandwiching" technique - he tries to use it with others but doesn't require it himself. Be clear with victories and accomplishments. But you don't have to attach a positive and constructive together just to deliver feedback.
- Rachael - verbal. Receiving - also likes direct feedback.
- How would you describe your work style?
- Rachael - spend a few minutes gather thoughts (for confidence) then group collaborating/discussion
- Carlos - working through it as we head into week 2 - explain to another person, they explain back, and he explains back for better understanding. Talking through explanations.
- What are each of our strengths? How can our strengths complement each other?
- Carlos - flexibility, adapability, patient, resilient.
- Rachael - setting expectations and keeping a group accountable
- What’s gone well or poorly in your previous projects?
- Carlos - CSS poorly, able to produce functionality that exceeded expectations
- Rachael - pom/scheduling studying/project work went not as well as I wanted,
- How will we set direction and make decisions as a team?
- Project boards, slack to check-in, use guideline for timeline re check-ins with PM as "north star", communicating.
- How will we overcome obstacles?
- Address early and if needed, split into smaller tasks.
- What do you need (resources, environment, communication) to do your best work?
- Communicating, setting intention for pom structures, then checking back in with each other.
- Quiet spaces at home, but Turing collaborative setting to bounce ideas of each other. Balancing these out.
- What scheduling restraints do you have? What are your scheduling preferences?
- 6 - 7:30 PM dinner/family time
- Carlos - Sundays band commitments (7 - 11PM)
- Rachael - Sundays 4:30 PM - night off for partner time
- What is your style for giving feedback? Does anything ever hold you back from giving feedback?
- Being direct and sharing feedback earlier rather than later to help course correct.
- 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?
- Rachael - practice JS functionality. Feels strong in CSS layout.
- Carlos - opposite - practice CSS layout but strong in JS functionality.
- What tools do you want to use to manage the project?
- GitHub project and Slack channel
- How do you want the group to solve problems when members run into issues with features of the project?
- Asking question format - clear direct communication. If working remote (with snow) using the established check-in time after poms to update and review. Wins/struggles.
- How do you know if a project is successful? How can we achieve that as a group?
- Successful if we both manage to learn and implement new tools. Keep an eye on MVP as guidance but make sure concepts are solid.
- How will we recognize each other's successes and celebrate them?
- During check-ins. Update each other on project boards updates/movements.
Any additional questions that you would like to add:
Project: Intention Timer
Group Member Names: Carlos Flores & Rachael Thomas
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?): Having a better understanding of the concepts and tools used in our code.
Team strengths & collaboration styles (consider discussing your Pairin qualities here): Verbal communication works best for both. Having defined checklist items and updating the board (and therefore each other) in a timely manner.
How we can use our strengths to overcome obstacles: Sharing feedback openly and commisterating
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Defined above.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): 3 times - morning, afternoon and evening check-in. Slack updates and/or video calls.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Rachael - JS functionality. Carlos - opposite :)
Workload Expectations (What features do we each want to work on?): Rachael - features of logging (JS), Carlos - features of layout. Work on where we feel we are lacking, but balance it out to help each other succeed and stay on time.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Improve Git workflow, project board usage, commit to review each other's code for feedback
Expectations for giving and receiving feedback: Being open to doing so in a timely manner and being open to direct feedback.
Project management tools we will use (GitHub projects or Trello are popular tools): GitHub projects.
Day 1 Agenda:
- DTR
- GitHub projects (setup board)
- Sketch out HTML
- Interation 0 state and start chunking steps.
Additional Notes: