Skip to content

Instantly share code, notes, and snippets.

@Kristiannmiller

Kristiannmiller/Hang-In-There-DTR.md

Last active July 14, 2020 20:54
Show Gist options
  • Save Kristiannmiller/4ae65416b6cefc491fbba5ea987e32ba to your computer and use it in GitHub Desktop.
Save Kristiannmiller/4ae65416b6cefc491fbba5ea987e32ba to your computer and use it in GitHub Desktop.
Download ZIP
Raw
Hang-In-There-DTR.md

Hang In There Project DTR

Project: Hang in There

Group Member Names: Kristi Miller, Estelle Staffieri

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

What we hope to get out of the project/What we want to achieve as a team:

  • Deeper understanding of project management and code functionality
  • Feel more comfortable with HTML
  • Confidence in the work we've completed

How will we know that we're successful:

  • When we can both answer the "why?" when looking through our code
  • When we can both explain thouroughly what our code is doing

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

  • Eye for detail and aesthetics
  • Similar ways of communicating
  • Similar ways of thinking
  • Willing and eager to put in the time
  • Excited to learn

How we can use our strengths to overcome obstacles:

  • Eye for detail will help us see spelling/syntax errors
  • Eye for aesthetics will prove helpful in making sure the site is lining up with visual expectations
  • Previous project experience will help us stay focused on comprehension and not completion
  • Support group will be helpful if we need another perspective on an issue.

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

  • Estelle: not available 5:30-6:30 on Wednesdays
  • Kristi: Half hour break after class, 9:00pm(ish) wrap up

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

  • Communication daily using Slack, Tuple
  • Cell phone number exchange, checking in with eachother, rescheduling if necessary, "open door communication"
  • Decision making through thoughtful discussion, bringing in an outside opinion if needed, trial and error
  • "Swingset" safeword will let us know when we need to say something that might upset the harmony of the group. After saying "swingset", the floor opens up for venting frustrations (any and all frustrations)

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

  • Estelle: good eye for detail, previous project experience, has an excellent support group behind her
  • Kristi: good eye for detail, eye for aesthetics, hard worker, Github project board understanding and use

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

  • We want to work equally together throughout the project
  • Want to commit equally and handle and equal amount of workload

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

  • CLEAN Git workflow, atomic commits
  • Tools: Slack, Atom, Git Kanban

Pomodoro Break Schedule:

  • 5 to 10 minute break every 30 to 40 minutes when working on technical aspects

Expectations for giving and receiving feedback:

  • Carefully considered and thought out words before giving negative feedback
  • Be mindful of the impact of your words on the other person
  • "Compliment sandwich" Don't stick to only negative OR positive feedback

Additional Remote Considerations:

  • If there are internet issues, call to problem solve

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

  • GitHub projects or Trello if GitHub is not learnable in given time

  • Day 1 Agenda: Get through the day 1 deliverables

  • Day 2 Agenda: Put some work into Iteration 0

  • Day 3 Agenda: Iteration 0 comprehension, dive into Iteration 1 if comprehension is solid

  • Day 4 Agenda: Iteration 1 and Iteration 1 comprehension

  • Day 5 Agenda: Iteration 2 and Iteration 2 comprehension

  • Day 6 Agenda: Iteration 3 and Iteration 3 comprehension

  • Day 7 Agenda: Iteration 4 and Iteration 4 comprehension

Additional Notes:

  • Agenda is loose outline. If things take longer than anticipated we invested the time into the issues to make sure that comprehension was met over completion.
  • GitHub Projects was attempted, however, didn't seem necessary with this kind of constant teamwork and working together.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment