DTR
Project: Battleship, BE 2001
Group Member Names: Ana Pérez Santos, Ethan Hocking
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?):
Individual Ana - Be more comfortable working independently, while working in a colloborative project; complete iteration 3; learn to review code Ethan - collaborate with people, making deadlines and meeting them
Team Be comfortable collaborating with people, Learn to review code, breaking projects down, making deadlines, and meeting them
Measure of Success Meeting deadlines During retros, checking in on how we feel about pull requests and merges
Team strengths & collaboration styles (consider discussing your Pairin qualities here): Ana - imaginative, vision, instropective, love of knowledge and wisdom Ethan - adaptable, creative, mediator
How we can use our strengths to overcome obstacles: Having two adaptable people working together who complement each other by providing confidence, accountability, and direction as needed, will help us reach our goals.
Schedule Expectations (When are we available to work together and individually? What constraints do we have?): Ana - available for all project work times, MTTHF 4-6, S - all day, S - 10 to 1 Ethan - M-F 7-9, Sat - all day (plan ahead if working in person), Sun - after noon (plan ahead if working in person) Daily Check-in: hopefully before 9 am Retro - Saturday
Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):
Preference: after pull request (slack or in person), check-in at beginning of day, retros on sat
Abilities & Growth Expectations (Technical strengths and areas for desired improvement): Ana - remote pair, solving git fires (if they occur) Ethan - scheduling and deadlines
Workload Expectations (What features do we each want to work on?):
Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques): Any issues with code will be added to the project board to be addressed Divide work into chunks that we can both work on independently During pair programming days, make time to decide next steps
Expectations for giving and receiving feedback: Norms 2001 Pull requests - specific
Project management tools we will use (GitHub projects or Trello are popular tools): Github GH Project Board
Day 1 Agenda:
- Meet with partner
- Discuss/Fill out DTR
- Review Project
- Fill in project details
Additional Notes: