Week 2-3: Battleship
Project: Battleship
Group Member Names: Sage Lee and Kiera Allen
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 hope to practice more efficient time management by setting deadlines for each iteration. We will try to finish Iteration 1 by Tuesday (3/24), Iteration 2 by Friday (3/27), and Iteration 3 by next Tuesday (3/31).
Team strengths & collaboration styles (consider discussing your Pairin qualities here): We both do well when we have some time to go over the material on our own before we collaborate, and we also want to try to have a conceptual understanding of the information before we move on to the next step. We both value communication and clarification, so we will work to continue exercising clarity.
How we can use our strengths to overcome obstacles: COMMUNICATE! We will make an effort to reach out during productive struggle, not letting it devolve into unproductive struggle.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): We have set a standing appointment from 6 - 9 during the week as a block of time to work together or separately, but we are "available" and prioritizing project work time during that block.
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?): Since clear communication is important to us, we will be flexible to reach out as needed. We have set the 30 minutes before class starts in the morning as potential project work time, in addition to our nightly standing appointments. When making decisions as a team, we will make sure to confer on core functionality and/or big changes.
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): We would both like to improve our command of syntax and formatting, and develop a better understanding of scope.
Workload Expectations (What features do we each want to work on?): Initially, Sage will construct a Ship test that tests a Ship class that she will subsequently create, and Kiera will construct a Cell test that tests a Cell class that she will subsequently create. Then we will come together to work through the more complex aspects of a Cell class. From there, our pattern will typically be we work individually on simple aspects of the project and then come together to work on the complex parts.
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): We want to commit after passing a test, completing a file, and also after intense code work. We will inform our partner through Slack after we have sent a pull request. Once either of us have received a Slack ping regarding a pull request, the partner responsible for reviewing the request will communicate a timeline for the review.
Expectations for giving and receiving feedback: We are both open to constructive criticism as often as needed. When receiving feedback, we will try to be understanding and assume positive intent.
Project management tools we will use (GitHub projects or Trello are popular tools): GitHub projects
Day 1 Agenda: Overview, look over each iteration together to get a baseline understanding, create a GitHub project management system, and then construct initial Ship/Cell tests and classes.
Additional Notes: Ready to commence Batteship build!