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?
- What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
- How do you communicate best? How do you appreciate receiving communication from others?
- How would you describe your work style?
- What are each of our strengths? How can our strengths complement each other?
- What’s gone well or poorly in your previous projects?
- How will we set direction and make decisions as a team?
- How will we overcome obstacles?
- What do you need (resources, environment, communication) to do your best work?
- What scheduling restraints do you have? What are your scheduling preferences?
- What is your style for giving feedback? Does anything ever hold you back from giving feedback?
- 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?
- What tools do you want to use to manage the project?
- How do you want the group to solve problems when members run into issues with features of the project?
- How do you know if a project is successful? How can we achieve that as a group?
- How will we recognize each other's successes and celebrate them?
Any additional questions that you would like to add:
Project: Little SHop
Group Member Names: Corina Allen & Mack Halliday
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?): MH: Goal is to figure out the db and actual syntax for Rails, CA: CSS Styling with Bootstrap, ensure that we both are fully gaining knowledge and experience regarding the learning goals
Team strengths & collaboration styles (consider discussing your Pairin qualities here): CA & MH: we are both top-down, big picture people but Mack also likes to know the smaller details well.
How we can use our strengths to overcome obstacles: Identifying gaps and ensuring we both understand the various aspects of our project will help over obstacles. CA: Per Pairin results, I can help us stay calm during stressful times within the project. MH: Adaptability will be helpful.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): CA: Not available on Saturday or Sunday evenings starting between 5/5:30. Can stay at least a little late most days. MH: Available to meet in mornings, Saturday potentially open to meet
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): Both are very available via Slack. We will do a mini-retro at the end of every day before parting ways just to ensure we are on the same page and clearly state what we can move forward with individually until we meet up to work together again.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): CA: Overall workflow is pretty solid, just want to work on Model Behavior and defining Controller#Actions. MH: Understand flash messages well, also have done sad path testing before. Areas for improvement: understanding database model relationships better
Workload Expectations (What features do we each want to work on?): pairing for db, one more complex user stories we will both do the work independently and then review together the next day for the final version
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Never merge your own PR, using Issues and closing when complete, when doing code review, utilize leaving comments within the code for discussing issues and improvement, pairing for db work, each user story is it's own branch
Expectations for giving and receiving feedback: Should be kind, empathetic, and with the intention/spirit of positively constructive
Project management tools we will use: GitHub's Project/Conveyor Belt
Day 1 Agenda: Setup stucture and co-authored commits, decided who's doing what for day 1 at home tonight, setup dbs today before going home for the day
Additional Notes: