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 your learning goals for this project? What drives us in this project? Jorge and I will be focusing on object constructor functions, creating different classes, learning how to manipulate and create object interactions through a game. We want to learn how to create simple games and animations.
-
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches? We both communicate well so keeping each other in the loop will be much easier for us. Both approaches will serve us well, considering how much we can accomplish individually but also what we can accomplish through teaming up.
-
How do you communicate best? How do you appreciate receiving communication from others? Open communication and a direct approach. Very good with receiving feedback. Jorge doesn't appreciate when people raise their voices at him.
-
How would you describe your work style? Concentrated and focused for short burst with intermittent rest throughout.
-
What are your strengths? How can our strengths complement each other? I have a decent conceptual understanding of object manipulation and orientation. Jorge excells with design and creativity.
-
What’s gone well or poorly in your previous projects? Most of my previous projects have gone well because communication was always present. Jorge experienced a side where he felt that a majority of the project landed on himself because the knowledge gap between him and his partner was at different levels.
-
How will we set direction and make decisions as a team? Through multiple forms of communication, in person, text, call, slack, etc.
-
How will we overcome obstacles? Together and if neither of us can figure it out than we will turn to our classmates!
-
What do you need (resources, environment, communication) to do your best work? Quiet space, an abundance of coffee, and a positive ambiance.
-
What scheduling restraints do you have? What are your scheduling preferences? None really, except Jorge has a significant other that he will have to attend to.
-
What is your style for giving feedback? Does anything ever hold you back from giving feedback? Nothing usually holds me back from giving feedback and I hope that my partners will do and feel the same.
-
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? Biggest strength would have to be my developing understanding of object constructors. Jorge is great with HTML and CSS. We could use some refinement with understanding how to use object constructors correctly along with creating refactoring aspects.
-
What tools do you want to use to manage the project? We will be using JS, some frameworks within that we haven't learned yet and variety of other tools at our disposal.
-
How do you want the group to solve problems when members run into issues with features of the project? Together and communicate. No sense in banging your head over something by yourself if it means it could be solved by another.
-
How do you know if a project is successful? How can we achieve that as a group? We feel satisfied and accomplished with what we learned through the process. Grade does matter but it's what we take away from it that counts for a lot as well.
-
How will we recognize each other's successes and celebrate them? With support and appreciation!
Any additional questions that you would like to add:
Project: Game Time
Group Member Names: Sam Singer, Jorge Perez
Project Expectations: We want to be able to create a game competently and condently
Goals and expectations: Learn object constructors and how to use them!
Team strengths: Different but complimentary
How to overcome obstacles: Together with communication
Schedule Expectations (When are we available to work together and individually?): Any time really.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open?): Whenever the need arises.
Abilities Expectations (Technical strengths and areas for desired improvement): Creating a structured clean looking code base
Workload Expectations (What features do we each want to work on?): Split evenly!
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests): We will be using github and waffle most likely
Expectations for giving and receiving feedback: Open and freely but in a respective manner.
Agenda to discuss project launch: DTR and then more in person!
Ideas: We will be creating a Flappy Bird iteration but using a Superman theme.
Tools: As many are permitted and available!
Additional Notes: