Skip to content

Instantly share code, notes, and snippets.

@augustreid

augustreid/fitlitDTR.md

Last active October 18, 2021 19:57
Show Gist options
  • Save augustreid/3f8580398623ac8d79e36920752b6e6f to your computer and use it in GitHub Desktop.
Save augustreid/3f8580398623ac8d79e36920752b6e6f to your computer and use it in GitHub Desktop.
Download ZIP
Raw
fitlitDTR.md

DTR

Project: Mod2 Group Project: FitLit

Group Member Names: Ivonne Hernandez, Jessica Organ, Eric Wang, August Reid

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

  • Get as far as possible but prioritize learning and a comfortable pace for everyone.
  • Create a really nice UI, usable and accessible.
  • Get more comfortable with TDD and figure out how to take advantage of that process.
  • Focus on class to class interaction.
  • All team members feel confident and understand the code, and we're generally happy with the final product.

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

  • There is a mix of preferred collaboration styles and strengths. The hope is to strike a balance between working all together and divide and conquer. Careful planning as a group, and consistent communication, should make it possible to divide and conquer while providing help for each other as needed.
  • Try some driver/driver?

How we can use our strengths to overcome obstacles:

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

  • Cutoff time 8pm MST
  • Mornings reserved for JSFun

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

  • Checkin at the end of each work time to discuss how much time is needed outside of class.
  • Primarily communicate through Slack
  • Decisions made by consensus, but willing to adapt if any team member has strong feelings in a specific direction.
  • Be honest and upfront at the beginning of any meeting about our mental/emotional state and ability to contribute.

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

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

  • PR Template
  • Everyone gets up to date locally at the beginning of each meeting
  • Code review before merges
  • Try to commit for each bullet point (at least)
  • New branch for each feature

Pomodoro Break Schedule:

  • 25 * 5
  • Eric is time keeper

Expectations for giving and receiving feedback:

  • Honest but kind
  • Immediate feedback for driver/nav
  • Written feedback when needed

Additional Remote Considerations:

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

  • GitHub projects

Day 1 Agenda:

  • Wireframe
  • Class structure
  • 3 Inspirations

Additional Notes:

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