Skip to content

Instantly share code, notes, and snippets.

@CalebCyphers
Last active July 7, 2020 23:40
Show Gist options
  • Save CalebCyphers/0b2bc7dc92e295d285290a00005c4951 to your computer and use it in GitHub Desktop.
Save CalebCyphers/0b2bc7dc92e295d285290a00005c4951 to your computer and use it in GitHub Desktop.

DTR

Project: HangInThere Paired Project

Group Member Names:

  • Caleb
  • Chris

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

  • Working Website that Successfully creates randomized posters, saves them, and has multiple pages
  • Develop a stonger understanding of HTML & CSS
  • Become more comfortable with Github

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

Caleb's Parin: Cooprative-Practical, Reliant, Team Player, Lover of Transcendance Chris's Parin: Imaginitive-Inspirational, Freind, Self-confident, Lover of Transcendance

How we can use our strengths to overcome obstacles:

  • We're both comfortable with listening to each other's ideas, and collaborating.

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

  • Directly after class works best, to discuss and share progress/goals. Then break off for solo work in the evenings.

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

  • Touch base over Slack when things are being pushed, and for questions.

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

  • Github
  • HTML & CSS
  • Fighting Procrastination

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

  • 50/50

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

  • Lots of communication

Pomodoro Break Schedule:

  • Every 20 minutes

Expectations for giving and receiving feedback:

  • Over slack
  • Zoom as Necessary

Additional Remote Considerations:

  • None

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

  • Slack
  • Zoom
  • Github

Day 1 Agenda:

  • Finish DTR
  • Fork Repos
  • Create private Slack Channel
  • Link DTR
  • Pages Deployed Site

Additional Notes: AHHHHHHHHHH!

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