Skip to content

Instantly share code, notes, and snippets.

@MillsProvosty
Created March 18, 2019 22:42
Show Gist options
  • Save MillsProvosty/2a923cfa88386c270205d935f94157c5 to your computer and use it in GitHub Desktop.
Save MillsProvosty/2a923cfa88386c270205d935f94157c5 to your computer and use it in GitHub Desktop.
Battleship DTR
Project: Battleship!!!
Group Member Names: Kyle Cornelissen, Mills Provosty
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?):
- Finish all 4 iterations
- Mills: I want to be able to offer more support in writing the methods, not just refactoring.
- Equal representation of learning/code production.
- We will know we're successful if we can explain any portion of the code and we finish all 4 iterations.
Team strengths & collaboration styles (consider discussing your Pairin qualities here):
- We both want to do Driver/Navigator
- Empathy! Strength of communication in terms of time limitations and commitment.
How we can use our strengths to overcome obstacles:
- Talking it out!
- Focused on our goals- sticking to them- adjusting if necessary.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?):
- Mills Can't Do: Sunday 9:30- 1:30 (2)
- Kyle - Try to skip weekends, otherwise travel.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
- Trello: keep track of progress, and DTR
- Mills & Kyle- please communicate ASAP
- Work time- if problems arise, communicate ASAP.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement):
- Make flashcards look easy!!!
- Have a successful experience working in a team with writing code!
Workload Expectations (What features do we each want to work on?):
-We are going to driver navigator most of this project.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):
-Use Trello, Driver/Navigator, Git commits together
Expectations for giving and receiving feedback:
- Daily check-ins
-Open communication
Project management tools we will use:
- Trello
Day 1 Agenda:
- Get the git! Get the setup complete by end of day.
Additional Notes:
NA
@allisonreusinger
Copy link

Great details here on getting this started, nice work!

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