Use this template 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?
Josh - My goal is to gain some experience working on a project with a partner and understanding good workflow practice.
Stephanie - Solidify JavaScript, opportunities to teach, with a drive to l collaborate and work as a team.
- What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
Pair programming seems to be the better choice, giving us both a great opportunity to teach and learn from one another.
- How do you communicate best? How do you appreciate receiving communication from others?
Consistent, communication is key. Preferably with video chat on making the process more personable.
- How would you describe your work style?
Scheduled, and consistent work time is key, but also keeping it balanced with other Turing and personal responsibilities.
- What are each of our strengths? How can our strengths complement each other?
We both bring a positive attitude to the project, along with a drive to learn, teach, and get stronger from this project. We are both huge on communication as well as making sure, we are both comfortable and happy with every step of the project. We both shared a lot of strengths in common as well as the same overall goals with this project.
- What’s gone well or poorly in your previous projects?
Allowing someone that seems to have more experience take the lead. We will both get the same amount of voice as well as ownership in this project. We will both make the decisions, and both get the equal amount of time as driver/navigator so we both can grow from this project.
- How will we set direction and make decisions as a team?
Open positive communication, this is our project. Making sure we set aside time to keep a plan we both agree on and are happy with.
- How will we overcome obstacles?
Reaching out to fellow cohort, mentors, and our rocks. Taking a step back.
- What do you need (resources, environment, communication) to do your best work?
We both have distraction free environments and setting a clear schedule is key. Staying organized.
- What scheduling restraints do you have? What are your scheduling preferences?
No Tuesday or Thursday Mornings, both willing to work weekends and a few hour weeknights. After a much-deserved break of course 5 – 7 worktimes, but able to expand within reason to reach our goals with the project.
- What is your style for giving feedback? Does anything ever hold you back from giving feedback?
Constructive feedback is key. Making sure we are giving feedback that is beneficial to one another.
- 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?
We both have a well-rounded knowledge of JS, but both also have some strengths we are excited to share and help each other grow with. Such as pseudo coding, project management, HTML, and I am sure a ton more we can both teach each other.
- What tools do you want to use to manage the project?
We will be using: slack, mdn docs, google console, debugger, atom, repl, and research material (www, books, mentors, cohort).
- How do you want the group to solve problems when members run into issues with features of the project?
Stepping back and communicating through the project. Take a break to do some research, taking the time to learn where we are struggling and lean on one another to help develop these new skills.
- How do you know if a project is successful? How can we achieve that as a group?
A project we are both happy with and both are 100% comfortable understanding. We only move forward together.
- How will we recognize each other's successes and celebrate them?
Celebrating our wins, take a moment to look at what we have accomplished every time we work on the project. Also taking a moment to acknowledge what we both bring to the team.
Any additional questions that you would like to add:
- What does remote focus look like for you? (headphones, distractions minimized (tv, family stuff, etc), video on)
A quiet organized work environment, minimizing distractions. Video on and screen sharing making the whole process fell more personable. Notebooks to take notes on project as we go.
- When working from the same place where you live, life can get in the way. What are some potential life things that could interfere with your ability to focus, and what plan can we come up with to approach those issues? (Examples: my kids, my dog, my partner, etc.)
Somethings that could interfere would be unruly animals, or surprise guest which shouldn’t happen at a time like this.
- If we encounter issues such as power outages, Zoom difficulties, or bad wifi, what backup plans can we have in place? (This could have answers like asking a neighbor to borrow wifi, using cellphone hotspot for internet, switching to slack or skype.
Phone numbers are exchanged, phone can be used as a decent hotspot if need be.
- Pomodoro breaks are especially important for remote work and doubly so for quarantine. What should our Pom cadence look like? How will hold ourselves accountable?
We will be using befocused to keep track of pomodoros, 25 minutes on 5 minutes off, but also willing to take longer breaks if needed.
- Quarantine is tough, so it’s important to make note of our mental/emotional state when working with others. How can we make space to check in on each other’s well being, in addition to the work that needs to be done?
I think it is important to take a moment at the beginning and end of each session of project time to check in on each other and keep clear healthy communication.
Project: romcom
Group Member Names: Stephanie Sohns and Joshua Sevy
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?):
To both gain some more experience working in pairs and managing a project efficiently. To have a better knowledge of Document Oriented Model, HTML, and JS. Success is counted if we both leave the project and are happy with the process of doing it, and a stronger understanding of the material in a whole.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
We are both lovers of justice so keeping a fair, growth for all mindset if key. Sharing these ideals along with both having varying experiences is going to be a huge strength for us both. Both being able to teach and learn.
How we can use our strengths to overcome obstacles:
Communication, being able to take a step back and come up with a plan. Using the tools we have to help get over these obsticles. Doing research to both learn and grow.
Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):
We have decided to work on our project weekdays 5 – 7 (longer if needed), and weekend morning to work together.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):
I think it is important to take a moment at the beginning and end of each session of project time to check in on each other and keep clear healthy communication. We will communicate over slack, and slack video chat/ screen share. Keeping in touch often to work through the project.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
Remote working, utilizing keyboard shortcuts, stronger overall knowledge of JS, HTML, CSS.
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):
All of these things are going to hugely beneficial.
Pomodoro Break Schedule: 25 minute on 5 breaks, 15 minute breaks every four.
Expectations for giving and receiving feedback:
Daily communication, giving quality feedback, and acknowledge our accomplishments after every work session.
Additional Remote Considerations:
Project management tools we will use (GitHub projects or Trello are popular tools):
GitHub projects, I think will be beneficial to start learning this early to develop a strong knowledge of how a project management tool can help with these projects.
Day 1 Agenda: Project Review, Git, Slack Setup, DTR and getting to know one another.
Additional Notes: