DTR Memo

gistfile1.txt

DTR Memo
Project: RomCom

Group Member Names: Jordon Smith, and Cameron

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

- Jordon: Become more confident in ablilty to write code.
- Cameron: Become more confident in developing logic for code implementation.
- Successfully implement and build git workflow skills.
- Base our goal acquisition on how we felt going into the project, and compaire at the end.

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

 - Implementing POM timers
 - Making sure everyone undersands 
  - taking time to make sure everyone is up to speed

How we can use our strengths to overcome obstacles:

- Objective analytical: understanding why/what works
- Resourcefulness 

Schedule Expectations (When are we available to work together and individually? What constraints do we have? Make sure to discuss the remote questions above in regards to this section):

- Generally, meeting after class.
- Adapt schelule based on progress.
- Constraints: various meetings.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team? How will we communicate about our emotional and mental well-being with each other?):

- Communicating daily
- Expressing any confusion on problems
- Meeting via video chat
- Find positive solutions
- Communication about stress/mental health

Abilities & Growth Expectations (Technical strengths and areas for desired improvement):

- Jordon: Have a better undersanding of how functions are implemented.
- Cameron: Have a better undersanding of the DOM and DM.

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

- Hope to get to iteration 5 and maybe get into the fancier stuff.

Workflow Expectations (Git workflow/Tools/Code Review/Reviewing Pull Requests/Debugging and Problem-solving Techniques):

- Taking turns with writing code and commiting code
- Refer to the insights tab on github to track commit ratios
- Resolve merge conflicts as a team

Pomodoro Break Schedule:

- Try taking a 5 min pom break every thirty
  - Longer break added in as needed 

Expectations for giving and receiving feedback:

- Open to feedback as needed

Additional Remote Considerations:

- Potential internet problems

Project management tools we will use (GitHub projects or Trello are popular tools):

- Utilize project board on github
  - update with progress

Day 1 Agenda: Set up project board for day 2; establish common goals/expectations.

Additional Notes: