Skip to content

Instantly share code, notes, and snippets.

@aprildagonese
Last active December 5, 2018 04:20
Show Gist options
  • Save aprildagonese/f8970219d2ba61b90e71da9386894c0f to your computer and use it in GitHub Desktop.
Save aprildagonese/f8970219d2ba61b90e71da9386894c0f to your computer and use it in GitHub Desktop.
Dagonese/Nager DTR - Battleship Project

Template for DTR Memo

Project: Battleship

Group Member Names: Zach Nager & April Dagonese

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?): We want to learn how to collaborate with another person both interpersonally and technically. We both also naturally gravitate toward individual work, so we want to learn how to do this successfully. We expect to aim for 4's in every category, but do as much as time allows. We'll feel successful if we receive a minimum of 3's on every category and/or learned a lot about working as a pair.

Team strengths & collaboration styles: Both have a goal of communicating clearly with each other. We're both committed to learning and high achievement. We're both very comfortable taking on a lot of responsibility for ourselves. We both have independent work styles and hope to build up our skills working collaboratively.

How we can use our strengths to overcome obstacles: We're both high achievers, so we hope to use this to approach communication as a challenge/goal.

Schedule Expectations (When are we available to work together and individually? What constraints do we have?): We agree to plan our next meeting session at the end of each session, meeting 1-2 times per day at least, not including weekends. We'll agree on weekends on a case-by-case basis.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): We're both available at all times, with no expectations for responses early in the morning or late at night. We both have an open door policy. We will make design decisions during pairing sessions and are free to experiment on our own before then, as long as we're working on the agreed-upon milestone.

Abilities & Growth Expectations (Technical strengths and areas for desired improvement): TDD for April, which Zach feels comfortable with. We'd both like to work on hashes, because we don't have much experience yet. Perhaps using more enumerables. More complicated class interactions.

Workload Expectations (What features do we each want to work on?): At this time, our plan is to both work on all features. We may divide up Iteration 4 or divide up other features as we move forward.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): We will attempt to divide evenly the responsibility for pushing/merging code. We will never merge our own code. We will give a heads up when something is ready for review/merge, as when as when the merge is complete. We both want to utilize TDD as much as possible.

Expectations for giving and receiving feedback: Each of us commits to telling the other person at the point that we feel the need to take on work, extra work, correct existing work, etc. This can be discussed whenever it feels appropriate, but both of us will commit to making an effort to discuss it in a timely manner.

Project management tools we will use: We don't currently have plans to use a tool, but are open to using a shared doc if we need one. Additional tools can be discussed as needed.

Day 1 Agenda: -Read through Iteration 1 on our own -Set up GitHub rep

Additional Notes:

@allisonreusinger
Copy link

I appreciate that you both thought through how to work on collaborating with each other more. Nice work!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment