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:
Group Member Names: Brandy Lacy Julian
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?): ** See also abilities and growth expectations. **
Team strengths & collaboration styles (consider discussing your Pairin qualities here). Brandi: Is extremely verbal and likes to talk outloud to someone to check if her logic is sound // people as rubberducking. Brandi is terrible at poms. Julian: appreciates being rubberducked to -- hehe-- Does like to go home to work depending on she is physically feeling today, struggles with sitting in room. Likes to spend time there but knows that sometimes home is the best place to be physically comfortable. PSEUDOCODING. ALL THE WAY THROUGH. Highest prioroty for working together. Lacy: No comparison, and taking regular poms. Not being too addictive to productivity but efficiently.
How we can use our strengths to overcome obstacles: Communication. Communication. Communication. Lacy: Brandi: Julian:
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Lacy : Not available Friday and Saturday July 12 & 13. Otherwise available until 6:30 every evening. Likes to work in person. Can not spend money to occupy space. Julian: Not available Saturday July 13th 11:00-3:00pm. Prefers to work remote on the weekend. Or in person not at Turing. Brandi: Available until 6:30pm. Prefers to work together on weekends in person. Expectation to work together in person until 6:30pm. Mornings left for self study. Not working over lunch. Weekends not too early of a start. 10am-4pm Saturday and Sunday. Planning early. Flexible to work more.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): Communicate often and openly.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Lacy: Hoping to gain confidence in javascript and writing functionality and push as far as possible on the project. Would like to also really develop the most efficient workflow possible. Julian: Big picture still tricky, last project changed it for the implementation of psuedocoding. More psuedocoding and wireframing. Lots of front loading. Then delegating. Brandi: Would like to see the big picture from the start, and zoom out and truly understand how everything is connected.
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): Be clear in the comments, write more than less, the more commits the easier it is to revert, and a lot of comments, even review comments to demostrate it was read. Key expectation is to NEVER MERGE YOUR OWN PR. Lacy: will have Repo.
Expectations for giving and receiving feedback: Open honest and as soon as calmly be delivered. Conscious of group dynamic of three. Implementing Group norms.
Project management tools we will use: Trello. Slack. Communication. Trello will be even better for group of three. Each with our own columns. And columns for interations. "Done" columns. Julian - trello board set up.
Day 1 Agenda:
Additional Notes: (Class/Group Norms)[] Goals: Goal to finish everything by Sunday July 21st and then polish until project is due. Done by Tuesday before project due with everything ready.