Skip to content

Instantly share code, notes, and snippets.

@eoneill23

eoneill23/FitLitDTR.md

Last active July 1, 2019 20:37
Show Gist options
  • Save eoneill23/d0cbd0f01d85f1e41aa0a9e9df002f8d to your computer and use it in GitHub Desktop.
Save eoneill23/d0cbd0f01d85f1e41aa0a9e9df002f8d to your computer and use it in GitHub Desktop.
Download ZIP
FitLit DTR
Raw
FitLitDTR.md

Template for DTR Memo Project: FitLit

Group Member Names: Eric O'Neill, Jon O'Drobinak

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 a better understanding of the relationship between data in different source files.
  • Try utilizing data visualization in some parts.
  • Use/hone jQuery.
  • Fine tune CSS.

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

  • Open communication
  • Sharing
  • Working together, working in Turing
  • Getting out of Turing occassionally

How we can use our strengths to overcome obstacles:

  • Communication - keeping an open channel of communication
  • Asking for help - struggling with pieces for an amount of time and then realizing we will need to ask for help.

Schedule Expectations (When are we available to work together and individually? What constraints do we have?):

  • Avaialable on the weekends, the 4th will be a light day, Eric is planning on being in on Fri, Sat, Sunday. Jon will join as he is available.

Communication Expectations (How and often will we communicate? How do we keep lines of communication open? How will we make decisions as a team?):

  • Timely Slack responses
  • Make decisions as a team

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

  • jQuery
  • CSS (Grid & Flex)
  • Git and GitHub
  • COMMIT THAT SH*T!!!

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

  • Split as evenly as possible.
  • Both parties get exposure to everything.

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

  • Git and GitHub - someone else review and merge
    • equal commits
    • local merges and conflict resolution
    • communication around pull requests and merges

Expectations for giving and receiving feedback:

  • We want it. Take it as a gift. It's like an error message.
  • Try not to take things personally and be kind.

Project management tools we will use:

  • Trello(?)

Day 1 Agenda:

  • DTR
  • Wireframe
  • Setup GitHub Repo

Additional Notes:

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