Skip to content

Instantly share code, notes, and snippets.

@tbierwirth

tbierwirth/DTR_Kelly_and_Tyler.md

Created May 6, 2019 22:32
Show Gist options
  • Save tbierwirth/fe10ec9b9d394d9adea5f236234faf0a to your computer and use it in GitHub Desktop.
Save tbierwirth/fe10ec9b9d394d9adea5f236234faf0a to your computer and use it in GitHub Desktop.
Download ZIP
Raw
DTR_Kelly_and_Tyler.md

Project: Battleship

Group Member Names: Kelly and Tyler

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?):

  • Kelly would like to learn more of the Ruby methods and how to implement them. Tyler would like to find more efficient ways to use methods, especially enumerables.
  • We would both like to achieve 3's on all parts of the rubric and feel confident with the code we have written.

Team strengths & collaboration styles (consider discussing your Pairin qualities here):

  • Kelly is an optimistic and creative partner and will help with motivation if things start to feel overwhelming. How we can use our strengths to overcome obstacles:
  • Strong communication, plan ahead with releastic goals and expectations. Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
  • We plan ~70% remotely and ~30% in person. Tyler prefers to workout after Turing and make a little time to spend with his girlfriend and friends. Kelly does not want to work in the mornings. Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
  • Daily check ins.
  • Being approachable in person and reachable on Slack.
  • Communication and compromise Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
  • Kelly is good at troubleshooting and debugging. Kelly would like to be more efficient with coding methods.
  • Tyler is good at being creative with methods and trying to be efficient. Tyler would like to be less stubborn with trying to solve a problem and be comfortable taking a break and come back to it later.

Workload Expectations (What features do we each want to work on?):

  • We want to look a little more into the requirements and fairly assign roles. Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
  • We are both comfortable committing often and expect to be knowledgable of all parts of the code. Expectations for giving and receiving feedback:
  • Giving and receiving constructive feedback from a place of positive intent and kindness. Project management tools we will use:
  • Slack, GitHub, Google Doc or Calendar Day 1 Agenda:
  • DTR, Create the repo, try to conceptualize some of the ideas required in the project. Additional Notes:
  • Celebrate small success. Don't be afraid of failure.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment