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?
- Ana - drivig the process a little bit more / AR
- Taylor - become comfortable setting up database / authorization / AR
- Antonio - combortable utilizing AR and action helpers
- Madeleine - comfortable many to many relationships / authorization
- What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- Ana - open to both method, paired programming in the beginning, divide and conquer after that, does not coming together to walk through people's code
- Madeleine - open to both divide and conquer and pair programming
- Antonio - open to both, but prefer divide and conquer - likes to take the time to research a concept
- Taylor - prefert divide and conquer - hard to get into flow when pair programming, however, reach out when getting stuck, coming together to walk through people's code
- How do you communicate best? How do you appreciate receiving communication from others?
- Ana - communicates regularly, check-ins in the morning or before worktime
- Taylor - brief 10 minute talk about goals before starting work / after work session, debrief on what got done/didn't go well/work on next time
- Madeleine - likes template of check-ins before and after, open communication
- Antonio - morning check-ins about what we accomplished, timely communication
- How would you describe your work style?
- Madeleine - working between 9am and 9pm, best flow working alone
- Taylor - best flow working alone, architectural questions as a group, not work past 6-7
- Antonio - best flow working alone, works late 8-11, going over code afterwards
- Ana - best collaborative work flow,
- What are each of our strengths? How can our strengths complement each other?
- Ana Communication - likes to check-in
- Taylor - flexible about everything, taking a large problem and breaking it down into achieveable chunk
- Madeleine - good at problem-solving
- Antonio - debuggin and attention to detail
- What’s gone well or poorly in your previous projects?
- Ana - everyone in group projects being flexible to change work stylesm, p
- Madeleine - being flexible and communicating consistently
- Taylor - problems in past: communication regarding struggles
- Antonio - not well: not having a good DTR or strategy for new things that come up / well: divided the project, open communication
- How will we set direction and make decisions as a team?
- Daily check-ins, laying out goals at beginning and debriefing at end of day
- Making decisions by majority or consensus
- How will we overcome obstacles?
- Pitching your question for everyone, and those who are comfortable can reach out for support
- Follow productive struggle, emphasis on reaching out in a timely manner
- What do you need (resources, environment, communication) to do your best work?
- Ana - Quiet place to work, break
- Madeleine - Feeling comfortable asking questions in the group and reaching out, break
- Taylor - an open accepting group that's willing to help when struggling
- Antonio - echoes, break after class to re-energize
- What scheduling restraints do you have? What are your scheduling preferences?
- Madeleine - early bed-time stop by 9
- Taylor - not many restraints, mentor meetings on Wednesday 5:30, try to stop between 6-7
- Ana - mentors/check-ins at 5:30, will communicate in advance with group
- Antonio - Monday/Tuesday mentor meeting, no meetings before 8
- What is your style for giving feedback? Does anything ever hold you back from giving feedback?
- Ana - feedback based on code to have a clearer understanding, open to feedback
- Madeleine - blunt feedback from a positive place, open and honest
- Taylor - good with code feedback, more reserved with interpersonal feedback
- Antonio - open to feedback, and feedback on feedback, blunt with feedback, not from a malintent place
- 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?
- Madeleine - I don't know what I don't know, comfortable putting all the pieces together
- Ana - I don't know what I don't know, skills in testing better than other skills
- Taylor - can improve more in AR, excellent at breaking big problems into small problems
- Antonio - can improve in AR / Joins, great in testing/edge cases
- What tools do you want to use to manage the project?
- Trello and Git Hub
- Would like to use Trello
- How do you want the group to solve problems when members run into issues with features of the project?
- Taylor - architectural-based decision should be brought to the group / stuck in struggling, just reach out to memebers
- How do you know if a project is successful? How can we achieve that as a group?
- Taylor - all meet learning goals / successfully completing the project / proud of work
- How will we recognize each other's successes and celebrate them?
- Recognizing successess in the moment during check-ins
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)
- Ana - headphone
- Taylor - doing code
- Antonio - coding, show in the backgroud
- Madeleine - cameos of family
- 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.)
- Ana - will mute self at 4
- Antonio - street is really loud, just need to reach out to drown out noice
- Taylor - no meetings expected over two hours
- Madeleine -
- 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.
- Communicate through slack on phone
- 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?
- Pomodoros to be taken as needed based on the person
- 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?
- Open to listening to others, will reach out on individual basis
- Check-ins can be a space to share about how we're doing
Project: Monster Shop
Group Member Names: Antonio, Madeleine, Taylor, Ana
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?): Team strengths & collaboration styles (consider discussing your Pairin qualities here):
How we can use our strengths to overcome obstacles:
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):
- Set time to be available - 1-4 project work time (school hours)
- Slack - 9-4 (check slack before bed)
- Code check-ins - will set time aside for going through people's code together as things are finished
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?):
- Different work times as far as evenings go
- Goals and Debrief wrapped up as one
- Check-in on days that we don't have work-time right after class with pomodoro included.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
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):
- Breaking functionality into general category for each user story, and reflecting that in our branching, is what we're planning to do
- Have a strategy to deploy to Heroku (built in Heroku feature that pushes up when merging to github master)
Pomodoro Break Schedule:
Expectations for giving and receiving feedback:
Additional Remote Considerations:
Project management tools we will use (GitHub projects or Trello are popular tools):
Day 1 Agenda: Work time at 1, Wednesday
Additional Notes: