#Rom Com With Aaron Townsend And Joe Lopez
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?
Properly use JavaScript to execute desired functionality in a clean, concise manner. This project will act as a great learning experience and we want to take away as much as possible. It provides us with real scenarios in which we will need to teach ourselves.
-
What is your collaboration style? How do you feel about pair programming vs. divide-and-conquer approaches?
We would like to implement both styles of programming; pair programming will allow us to work together and tackle problems together, but may be slower. Divide-and-conquer will allow us to work more efficiently, but we may be more likely to encounter bugs in our code.
-
How do you communicate best? How do you appreciate receiving communication from others?
We both communicate best verbally while doing our work. End of the day meet ups to talk about our work will be important in our process. We both appreciate open communication and blunt feedback.
-
How would you describe your work style?
We prefer to use a focused approach where we work on our project continuously. (In the zone)
-
What are each of our strengths? How can our strengths complement each other?
Aaron's strengths include being a creative thinker, a problem solver, and a helpful hand to others when they are in need. Joe's strengths include being very optimistic, being a problem solver, and staying motivated even when stuck on a problem. Our strengths complement each other as we share some of the same attributes and we will be able to stack them together.
-
What’s gone well or poorly in your previous projects?
In the past we have encountered communication, lack of effort, and poor decision making issues. Conversely, we have encountered great communication, dedicated team members, proper allotment of time, and good overall decision making.
-
How will we set direction and make decisions as a team?
We will set direction and make decisions based on proposed ideas that both team members approve of and give the thumbs-up to.
-
How will we overcome obstacles?
We have a very forward approach and will deal with them as a team whenever they arise. Open communication about any problems we have.
-
What do you need (resources, environment, communication) to do your best work?
Aaron can find focus anywhere. Joe prefers to work in a quiet environment. We both prefer to have good internet.
-
What scheduling restraints do you have? What are your scheduling preferences?
We both cannot work during class time. Aaron has scheduling conflicts Friday and Saturday night. Joe has scheduling conflicts Thursday after class. We both prefer to work after class and on Sunday.
-
What is your style for giving feedback? Does anything ever hold you back from giving feedback?
We are both very straight-forward and open. We both hold back from giving feedback when we aren't confident that we know the answer or have a better solution.
-
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?
We are both good at determining how we should approach and look at the problem at hand, especially in pseudocoding terms. We both could improve at finding the right tools to complete desired functionality. Your team could help support us in improving these skills simply by being available for our questions.
-
What tools do you want to use to manage the project?
Slack, Zoom, JavaScript documentation, our class notes, and potentially Tuple.
-
How do you want the group to solve problems when members run into issues with features of the project?
Reach out and communicate with each other. If we don't know, reach out to other classmates or instructors.
-
How do you know if a project is successful? How can we achieve that as a group?
We will know if our project is successful if we feel satisfied with it and we know that we have done the best that we possibly could have. As well, we will feel more accomplished by recognizing how much we have learned. Put in the effort.
-
How will we recognize each other's successes and celebrate them?
We will recognize each other's successes through acknowledgement and celebrate them by taking breaks and through leisurely activities.
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)
Aaron prefers having headphones on and working in solitude. Joe prefers working in solitude without people around him.
-
When working from the same place where you live, life can get in the way. What are some potential life things that could affect your ability to focus, and what plan can we come up with to approach those moments?
For Aaron, he is going to be having distractions from his family. For Joe, he is going to be having distractions from his significant other's family.
-
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.
If we have bad wifi we will both try to use our mobile hotspots. In the event of a power outage we will either try to charge our laptops with our cars or find a different location.
-
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?
We both find that Poms work well, however, we both prefer to work work for approximately an hour and then taking a 10 min Pom. To hold ourselves accountable we will point it out to each other to take breaks and set timers.
-
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?
Regular check-ins will be super important here and open communication as well.
- DTR
- Fork Repo and clone down
- Communicate instructor
- Create tentative schedule
- Iteration 0
- Iteration 1
- Iteration 2
- Iteration 3
- Iteration 4
- Iteration 5
- Optional Extensions
- Refactoring
- Code clean up
- Submit project