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 is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- We both like to do paired, driver/navigator for the large majority of the project, but if we ar stuck on something will take time to work it out ourselves, and will divide and conquer in areas that we see fit.
How do you communicate best? How do you appreciate receiving communication from others?
-
Ashley: Very open and available to communicate how I'm feeling and where I need support. Very flexible do adapting to daily needs.
-
Tim: Open and honest communication is best. Will not hesitate to express how I'm feeling about tasks.
How would you describe your work style?
-
Ashley: A workhorse and has trouble stepping away from a project, but working on more self care. Also very collaberative and prioritize the whole group understanding.
-
Tim: Likes to maintian a good level of organization to keep focus. I prefer pomo break for maintaining good self care.
What’s gone well or poorly in your previous projects?
-
Bad: Divide and conquer has been fairly disorganized in the past. Need a better plan for taking the step to reach out when we get stuck on something.
-
Good: Having an organized daily agenda, and a schedule that remains dynamic based on how the project is going so far.
How will we set direction and make decisions as a team?
- Having a retro/checkin at the end of a night of work that set goals going forward.
What do you need (resources, environment, communication) to do your best work?
- Open and honest communication. Maintaining a goal of vocal collaberation.
What scheduling restraints do you have? What are your scheduling preferences?
- Dinner: 6:30 - 7:30, shoot for a hard stop at 9:00. No rigid schedule restraints.
- Weekends: Try to shoot 8-12 hours over the weekend.
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
- We both are comfortable with hearing and giving honest verbal feedbcak baout our performance, and we expect ourselves and eachother to hold the other accountable.
How do you know if a project is successful? How can we achieve that as a group?
- If we both can say that we gained a substantial amount of understanding, and that we are both able to speak to every line of code and how to implement it.
How will we recognize each other's successes and celebrate them?
- Positive open and honest verbalization. Taking the time to help eachother and celebrating when when we reach understanding of something that we were iffy on.
Any additional questions that you would like to add:
Group Member Names:
- Tim Keresey
- Ashley McDonald
Workload Expectations (What features do we each want to work on?):
- Tim: Iteration methods, Still a bit iffy on determining when to implement DOM manipulation, coupling classes.
- Ashley: Iteration methods, displaying data model on DOM, CSS.